<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- generator="FeedCreator 1.6" -->
<rss version="0.91">
    <channel>
        <title>Open Tag Directory: Libraries</title>
        <description>The Open Tag Directory provides a &quot;directory style&quot; interface to popular social bookmarking websites.</description>
        <link>http://www.open-tag-directory.org/tags/Libraries</link>
        <lastBuildDate>Thu, 08 Jan 2009 16:07:01+0100</lastBuildDate>
        <generator>FeedCreator 1.6</generator>
        <item>
            <title>Developer's Guide - AJAX Libraries API - Google Code (1 Citations)</title>
            <link>http://code.google.com/apis/ajaxlibs/documentation/index.html#jquery</link>
            <description>&lt;p&gt;The AJAX Libraries API is a content distribution network and loading architecture for the most popular open source JavaScript libraries. By using the google.load() method, your application has high speed, globally available access to a growing list of the most popular JavaScript open source libraries., &lt;a href='http://blogmarks.net/marks/search/libraries'&gt;blogmarks.net&lt;/a&gt;&lt;/p&gt;</description>
        </item>
        <item>
            <title>Open Library API (OpenLibrary) (1 Citations)</title>
            <link>http://openlibrary.org/dev/docs/api</link>
            <description>&lt;p&gt;The Open Library is a project of the Internet Archive. Its goal is to create an online catalog that contains one web page for every book ever published. To do this, it accepts data from a variety of sources: libraries, publishers, book-sellers, and individuals., &lt;a href='http://blogmarks.net/marks/search/libraries'&gt;blogmarks.net&lt;/a&gt;&lt;/p&gt;</description>
        </item>
        <item>
            <title>OCLC and the Great Library Scandal | booktwo.org (1 Citations)</title>
            <link>http://booktwo.org/notebook/oclc-and-the-great-library-scandal/</link>
            <description>&lt;p&gt;Why are our publicly funded libraries locked into a monopolistic relationship with a clearly greedy data supplier? Why are they paying thousands of pounds to access their own data? Why are the public, whose money is paying for this, locked out of the system?

Plutôt que de se battre sur le code source libre, les données *publiques* livres placées dans des silos, c'est plus dommageable., &lt;a href='http://blogmarks.net/marks/search/libraries'&gt;blogmarks.net&lt;/a&gt;&lt;/p&gt;</description>
        </item>
        <item>
            <title>Using the Zend Framework with Symfony 1.1 | MirthLab (1 Citations)</title>
            <link>http://blog.mirthlab.com/2008/10/21/using-the-zend-framework-with-symfony-11/</link>
            <description>&lt;p&gt;I?ve written about using the Zend Framework within Symfony before but things have changed a bit in Symfony 1.1 so I wanted to post an update with a new Symfony 1.1 compatible approach to loading and using the library from within Symfony. The biggest change that has happened since my previous article is that the sfZendFrameworkBridge has been removed from Symfony. This is actually a Good Thing since, as you?ll see in a moment, there is now a more elegant approach to loading external libraries., &lt;a href='http://blogmarks.net/marks/search/libraries'&gt;blogmarks.net&lt;/a&gt;&lt;/p&gt;</description>
        </item>
        <item>
            <title>pChart | a PHP Charting library (1 Citations)</title>
            <link>http://pchart.sourceforge.net/index.php</link>
            <description>&lt;p&gt;pChart is a PHP class oriented framework designed to create aliased charts. Most of todays chart libraries have a cost, our project is intended to be free. Data can be retrieved from SQL queries, CSV files, or manually provided. This project is still under development and new features or fix are made every week.

Focus has been put on rendering quality introducing an aliasing algorithm to draw eye candy graphics. Rendering speed has been dramatically enhanced since the first version, we'll still continue optimising the code!, &lt;a href='http://blogmarks.net/marks/search/libraries'&gt;blogmarks.net&lt;/a&gt;&lt;/p&gt;</description>
        </item>
        <item>
            <title>Language (API)  Processing 1.0 (1 Citations)</title>
            <link>http://processing.org/reference/changes.html</link>
            <description>&lt;p&gt;The biggest changes in the months prior to release 1.0 are as follows:


Libraries - All libraries must be placed in a folder named &quot;libraries&quot;, inside the sketchbook folder. Do not use the main &quot;libraries&quot; directory in the Processing distribution, as it is reserved for the core libraries, and is not visible on Mac OS X.

XML - The XML library is now included by default, so you won't find it in the Import Library menu anymore. In addition, the XML library since 0135 has been greatly improved, making it compatible with far more documents.

Processing.app - The Mac OS X release of Processing is now a single .app file, more befitting an OS X application.

Processing.exe - The Windows release has a new launcher based on launch4j. Unfortunately, some machines have a problem with the new launcher that we haven't been able to track down. If you have trouble, please help us find the problem. PDE files are also now double-clickable on Windows.


OpenGL - All OpenGL sketches now use 2x full screen anti-aliasing. This means that these sketches are always smooth, and the smooth() and noSmooth() commands are ignored. To return to the behavior found in the beta releases, see the hint() reference.

P2D and P3D - The P2D renderer has returned (see the size() reference) and smoothing is now enabled for both P2D and P3D. Smoothing support is unfortunately incomplete, however, and sometimes thin lines can be seen inside shapes. This is a very high priority bug to be fixed in a future release.

Candy and PShape - The Candy SVG library has been merged into the core, which brings along a new loadShape() command and a new PShape object. The special powers of PShape will be rolled out in future releases. For the time being, loadShape() works best with the default renderer (JAVA2D). Complex shapes will often appear jagged or not at all when rendered with P2D, P3D, and OPENGL. We've also added better support for SVG files created with Inkscape.


PVector - We've added a new class called PVector, which is a simple three-dimensional vector (also known as point or tuple) class. This is useful for storing point data, or operations on 3D points.

Tools - A new Tools API has been created for developers who want to contribute code that extends the Processing Development Environment in some fashion. Let your creativity flow with fantastical contributions like &quot;Color Selector 2.0&quot;, &quot;ROT13 Code Mangler&quot;, and &quot;I Am Rich&quot;. Visit the developer page on tools for more information. Similar to libraries, tools are installed in a folder of the same name within your sketchbook folder.

Asynchronouse Images - Big JPEGs and small pipes? We've added a new requestImage() that loads an image in the background so that your sketch doesn't freeze when loading lots of large images over a slow connection. 


Present - Present mode (full screen) is handled differently. When run inside the PDE, only Mac OS X uses exclusive mode with Present. Windows and Linux just do full screen windows. When run outside the PDE, all three simply create an undecorated window the size of the entire screen, and on the Mac, an option is added to the Info.plist file to hide the dock and menubar (since that cannot be done programatically from Java). 

Compiler - We've removed the old Jikes compiler and are now using another. We've also tried hard to improve the quality of error messages, though some are still real gems that invoke the complaints of mainframe computers in 1970s films.

Internationalization - For better internationalization support, we've changed to UTF-8 encoding when loading and saving sketches. Sketches that contain non-ASCII characters and were saved with Processing 0140 and earlier may look strange when opened. Garbled text and odd characters may appear where umlauts, cedillas, and Japanese formerly lived. If this happens, use the &quot;Fix Encoding &amp; Reload&quot; option under the Tools menu. This will reload your sketch using the same method as previous versions of Processing, at which point you can re-save it which will write a proper UTF-8 version.

Java - Linux and Windows now inlude Java 6 update 10 with the download. We still don't have support for Java 1.5 syntax yet, but we hope that the performance boosts in Java 6 will help applications run well., &lt;a href='http://blogmarks.net/marks/search/libraries'&gt;blogmarks.net&lt;/a&gt;&lt;/p&gt;</description>
        </item>
        <item>
            <title>Ajaxian » MooTools and Sizzle (1 Citations)</title>
            <link>http://ajaxian.com/archives/mootools-and-sizzle</link>
            <description>&lt;p&gt;Valerio Proietti has written a thoughtful post on why MooTools won?t use Sizzle (and tries to argue why other libraries shouldn?t).

...

I don?t expect every library will drop its own engine and plugin Sizzle right away. However, if done correctly, Sizzle can be an area of collaboration. If it becomes ?John?s Library? that is one thing, but you will note that there have already been patches from the Prototype folks and maybe others. Sizzle could be a playground for innovation itself., &lt;a href='http://blogmarks.net/marks/search/libraries'&gt;blogmarks.net&lt;/a&gt;&lt;/p&gt;</description>
        </item>
        <item>
            <title>Developing an Image Gallery with eZ components (1 Citations)</title>
            <link>http://www.ezcomponents.org/resources/articles/article-2006-04-19-image-gallery#finding-persistent-objects</link>
            <description>&lt;p&gt;This tutorial shows you how to program a web application that stores photographs in an image gallery. It's based on libraries included with the eZ components, and so gives you a practical example of the library usage., &lt;a href='http://blogmarks.net/marks/search/libraries'&gt;blogmarks.net&lt;/a&gt;&lt;/p&gt;</description>
        </item>
        <item>
            <title>AJAX Libraries API - Google Code (1 Citations)</title>
            <link>http://code.google.com/apis/ajaxlibs/</link>
            <description></description>
        </item>
        <item>
            <title>????????? Google AJAX Libraries API ?? JS (1 Citations)</title>
            <link>http://blog.miniasp.com/post/2008/10/Consider-using--Google-AJAX-Libraries-API-when-deploying-website.aspx</link>
            <description></description>
        </item>
    </channel>
</rss>
