Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

AdobeLibrary1.jsx etc License and Distribution

New Here ,
Sep 29, 2005 Sep 29, 2005
[Preamble - I may be totally wrong about the following - I do hope so, please put me right if so]

It would make life a lot easier if we could include the Adobe Library scripts along with scripts we release ourselves - when they are required. At the moment the Library scripts' licenses do allow us to include them ('we may distribute them'), but then the user is not allowed to use them without written permission from Adobe. That really isn't workable. Furthermore, the only place I have found that provides the files for download is as part of the ImportCamera package. Again, that is not a particularly workable or helpful route for other scripters to direct users to. If they have to be downloaded separately, please could Adobe include them as an individual item from Studio Exchange. Is there really a strong reason for not just making these Libraries copyright Adobe but open to anyone to distribute *and use*?

My experience in releasing scripts is that if the process is not totally simple (one set of files to be put in one location) then it doesn't happen and you end up with frustrated and pissed off users. Because of that I think I am going to have to fall back on not using the libraries (and reinventing the wheel - usually not so well as a consequence) until a more workable way of getting them to the user is made possible.

While it appears the libraries come as part of the package for CS2, this does not seem to be the case with PS CS2, also I believe the Library3 was not written when the initial release of CS2 was made, so again there may be gaps.

Andrew
TOPICS
Scripting
750
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Sep 29, 2005 Sep 29, 2005
Reading the license statement at the top, I see your point. That was not the intention. Feel free to distribute the files, your users need not worry.

If you purchase CS2, you get the ScriptManager and workflow scripts, which include libs 1 and 2. Without the workflow scripts, the libraries aren't included (PSCS2, IDCS2, etc). But I think what we're experiencing here is a disconnect between the intent and the result. We never really got a good handle on how to ship the libs without a script to run.

Lib3 was added later to provide a little more functionality (check out verifyFolder() for example), and to patch some bugs in libs 1 and 2.

You should ship all 3 libs if you're going to use them.

You can also copy the functions you need into your own scripts.

The libs are there to help. Not get in the way.

Bob
Adobe WAS Scripting
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Sep 29, 2005 Sep 29, 2005
Ya' know, they could have put it under the LPGL or a similiar license. The one
I'm going with from here on out is
http://creativecommons.org/licenses/LGPL/2.1

I'll only do this for major pieces of work, not 20 liners or anything like that.

ciao,
-X
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 29, 2005 Sep 29, 2005
Bob, I appreciate that is "your" intent to let us distribute and use these library files as we wish, but for people contemplating some money making enterprises that include Bridge scripts, your posting here isn't enough for me. So, like Andrew, I've taken to NOT using them because of that legal ambiguity.

Is there some more formal way to fix this? Like re-release the files under one of the common licenses and let us redistribute files that contain a usable license. I think in this case you want a very open license since you're more interested in encouraging people to build off what you have and make useful stuff rather than trying to guarentee open-ness of derivative works. The LGPL, referenced above, would do as would several of the other "open licenses" that are less restrictive than the GPL.

I know this involves the legal dept at Adobe and is probably a pain to get done, but you're really going to limit the use of those libraries for anyone intending redistribution until it's fixed.

In case it's relevant, the Image Processor script has no licensing clause in it at all, but the stock photo scripts have the same one that AdobeLibrary*.jsx have.

--John
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Sep 29, 2005 Sep 29, 2005
Lemme check with the powers that be.

More later, as I'll be in SJ tomorrow with said powers.

Bob
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 04, 2005 Oct 04, 2005
OK,

We're running it all by legal with the hopes of getting some new language at the top of those library files that will allow you to freely distribute them. Not sure how long this will take, but we're working on it.

Bob
Adobe WAS Scripting
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 04, 2005 Oct 04, 2005
That's great news Bob, thank you and the Adobe team too for responding.

Andrew
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 04, 2005 Oct 04, 2005
LATEST
Sounds like good progress Bob. Thanks.
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines