Slashdot Mirror

← Back to Stories (view on slashdot.org)

Adobe Unveils Open Source Library

Posted by CmdrTaco on from the catching-up-to-the-little-old-gimp dept.

anamexis writes "Adobe premiered (no pun intended) opensource.adobe.com recently. The first two libraries available, titled Adam and Eve, respectively, take on complex GUI issues in applications. They are written in C++ and have been released under the MIT License, an OSI-Approved Open Source License."

6 of 406 comments (clear)

  1. Acrobat Reader by jamesshuang · · Score: 4, Interesting

    If only they'd fix Acrobat Reader for linux...

    1. Re:Acrobat Reader by PoprocksCk · · Score: 5, Interesting

      You're right, it is less bloated. But the point is that they're still using some ugly, closed-source GUI library, and that they fully neglected Linux users for one whole major version.

      Sure, they announced a 'beta' of version 7 for Linux, but has anyone ever *seen* it? They cancelled the public beta after a few days. So it's not so much that the product is a poor one (version 5.0.10 is pretty decent, really) but that they see Linux as a tier-2, unimportant platform. I truly hope that that changes in the near future as Adobe begins to embrace OSS.

  2. Re:The GIMP by Homology · · Score: 5, Interesting
    Too Lazy? It's one of the shortest licenses known to man:

    The OpenBSD license is even shorter :

    Below is an example license to be used for new code in OpenBSD,
    modeled after the ISC license.

    It is important to specify the year of the copyright. Additional years
    should be separated by a comma, e.g.
    Copyright (c) 2003, 2004

    If you add extra text to the body of the license, be careful not to
    add further restrictions.

    /*
    * Copyright (c) CCYY YOUR NAME HERE <user@your.dom.ain>
    *
    * Permission to use, copy, modify, and distribute this software for any
    * purpose with or without fee is hereby granted, provided that the above
    * copyright notice and this permission notice appear in all copies.
    *
    * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
    * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
    * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
    * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
    * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
    * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
    * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
    */
  3. Where are the previous open source projects? by SimHacker · · Score: 4, Interesting
    For several years, Adobe used to have several other open source projects on their old web site, that have now been removed from their current web site, http://www.opensource.adobe.com. The missing projects include:

    Simulated Partial Specialization for non-compliant C++ compilers. Allows a user to obtain many of the benefits of partial specialization of C++ templates without direct compiler support.

    Python action plug-in for Adobe Photoshop. Allows a user to write Photoshop action plug-ins using Python. Has Python interfaces to all the actions APIs.

    Python plug-in for Adobe Illustrator. An Illustrator plug-in adapter that allows users to access the C level API from Python

    Python plug-in for Adobe After Effects. An After Effects plug-in that allows users to access the C level API from Python.

    Python module for Perforce SCM. A C coded Python module that provides access to all the calls in the Perforce source code management system SDK.

    -Don

    --
    Take a look and feel free: http://www.PieMenu.com
  4. Sounds like an ambitious undertaking by TeeJS · · Score: 5, Interesting
    From the article: (referring to Adam) "The code providing this functionality accounts for a third of Adobe's code base and nearly half of the bugs found during development."

    combined with: "The Eve layout engine has already saved Adobe millions of dollars in localization costs."

    Means this contibution (mainly UI work based on Boost) is a very decent contibution.

    --
    T.J. Schmitz - the man, the myth, the legend - o
  5. Re:The GIMP by molnarcs · · Score: 4, Interesting
    Some folks misundertand parts of the reason some developers use the BSD licence: it is not just more altruistic or something, it can be more practical. I remember an outburst from an mplayer developer saying that he sees no point in the gpl, for they have no means to prevent misuse anyway. Also, once you use the GPL, you have to keep on eye on violations, you have to keep vigilant, otherwise, what's the point of using it? So, some devs think that they don't want to be concerned with possible violations, they don't recurrent themes of whether or not it is okay to write binary only drivers for the kernel because of the GPL, and so on. They want to program and that's it. This might be the spirit some refer to as "academic".

    Some developers go farther than this, and think that even the two clause BSD licence is too much legalese. Hence, code written by Poul-Henning Kamp is distributed under the beerware licence :))) (hence my reply to your post) - this is how it look like:

    * "THE BEER-WARE LICENSE" (Revision 42):
    * phkATFreeBSD.ORG wrote this file. As long as you retain this notice you
    * can do whatever you want with this stuff. If we meet some day, and you think
    * this stuff is worth it, you can buy me a beer in return Poul-Henning Kamp
    */</blockquote>
    Whether or not you agree one agrees with him (I understand the point and usefulness of the GPL very well btw) - one has to admit that sometimes this kinda licence might give more freedom not only to the user, but to the developer(s) as well in the sense that a 3rd party vendor writing a binary driver or piece of code won't cause a shitstorm on the BSD kernel mailing list (as Brandybuck put it in one of his posts:))))