IT Mill Toolkit is an open-source framework, providing widgets and tools for the development of Rich Internet Applications (RIAs). Deliver web applications without worrying aboutincompatibilities of web browsers, DOM or JavaScript by using standard Java tools. 

• homepage
• demo
• download

LIVE PIPE UI

LivePipe UI is a suite of high quality widgets and controls for web 2.0 applications built using the Prototype JavaScript Framework. Each control is well tested, highly extensible, fully documented and degrades gracefully for non JavaScript enabled browsers where possible.

• homepage
• demo
• download

iWebKIT

Iwebkit is the revolutionnairy kit used to create high quality iPhone and iPod touch websites in a few minutes. In the first 4 months of it’s existance the pack has greatly evolved from a basic idea to a project that has reached worldwide fame.

• homepage
• demo
• download

JITSU

Jitsu contains an integrated set of tools to enable developers to build and deploy sophisticated user interfaces for web applications. These include an Xml markup language, page compiler, data binding engine, JavaScript runtime, control library, runtime inspector, animation engine, cross-platform library, Ajax, and back button support. Jitsu apps use DHTML and run in most modern web browsers.

• homepage
• demo
• download

MochaUI

MochaUI is a web applications user interface library built on the Mootools JavaScript framework.

• homepage
• demo
• download

Echo Web Framework

Echo is an open-source framework for developing rich web applications. From the developer’s perspective, Echo behaves as a user interface toolkit–like Swing or Eclipse SWT. AJAX technology is employed to deliver a user experience to web clients that approaches that of desktop-based applications. Echo applications can be created entirely in server-side Java code using a component-oriented and event-driven API (applies to Echo2 and Echo3) or as client-side applications written in JavaScript (applies to Echo3 only).

• homepage
• demo
• download

The Yahoo! User Interface Library (YUI)

The YUI Library is a set of utilities and controls, written in JavaScript, for building richly interactive web applications using techniques such as DOM scripting, DHTML and AJAX.

• homepage
• demo
• download

TypePublish

TypePublish aims to fill a gap in the market for an open-source PHP CMS that is accessible for novice web users while at the same time providing a powerful application framework on which web developers can create compelling, custom web media.

Features:

Links:

• homepage: http://www.typepublish.org
• download: http://www.typepublish.org/download/v05

Zenphoto

Features:

• Internationalization/localization
• Multi-lingual titles and descriptions
• Plugin system
• Slideshow
• Automatically generated thumbnails, custom crops possible!, and sized-down images
• Upload via FTP or via the admin interface
• Move/copy/rename images and albums without loosing any data
• Upload images, albums (folders) or even zip-archives
• Comments on images and albums with powerful spam filters
• AJAX-powered edit-while-you-browse
• Sub albums; interface for moving/renaming images and albums.
• Video support for Flash Video (.flv), MPEG4 (.mp4), Quicktime (.mov) and 3GP (.3gp)
• Audio support for MP3 and MP4
• Password protection for gallery and albums
• EXIF and IPTC support
• Watermarks for images
• Powerful search with boolean expressions
• Tags: Categorize you images with tags
• Image and album rating
• Dynamic albums: Generate albums from searches!
• Highly customizable theme engine
• rss for gallery, albums and comments
• Multiple administrative users with varying rights
• Cruft free, search engine friendly URLs with mod_rewrite

Links:

• download/homepage: http://www.zenphoto.org
• demo gallery: http://www.zenphoto.org/zenphoto/

1. Simple:

   You do not have to be an expert at PHP, HTML, JavaScript, and CSS to use the framework. You can do most, if not all, your coding in PHP, and the framework will generate HTML, CSS, and JavaScript for you. There are object for most of the HTML element, with method to manage common task, like updating the content of a Div or items in a forms Select pull down. A lot of the other frames include a simple example that is anything but simple. For my simple example I have been asked where the rest of the code is!

2. Develop how you want:

   the framework supports 3 different development models: i. the developer develops the whole application and interface in PHP, since the framework knows about HTML elements you want to interact with, i.e. there are objects for Select, Div, Table with instances with unique IDs; it is easy to have the framework generate simple html and CSS for you. ii. A designer generate a pretty but dump page, and you then hook events to it to make it a real application (see Last Binding of Event below) iii. You design an interface as a template (example Smarty), and have the framework make html, CSS, JavaScript that you pore into the template.

3. Event Driving:

   I would rather have events delivered to the back-end, and decide there what actions to take then to write a lot of JavaScript in the front-end. What happens after an event?:

   1. The front-end gather information about the state of the page
   2. The back-end see if there is an event handler registered for this event
   3. If there is a registered event handler, it is call with the information from step i.
   4. After processing data is return back, if any, to page for processing:

   When an event happens there are 3 action that can be taken:

   1. Preprocessor Action: example setting a spinning hour glass gif, to tell the use that something is happening.
   2. Post-processor Action: do something standard with the data that comes back, like update a div.
   3. Back-end delivers code to front-end: have the back-end tell the front-end what it want to do, or message the user.

4. Late Binding of Events:

   The pages HTML does not need to changed event and there logic (event handlers) are bound at run time. So your wed designer could delivery a pretty, but dump from, and without changes to the HTML you can make it into a AJAX enabled application. This make for simpler mark-up and an easier separation of design and code.

5. Object Oriented:

   There are not only objects for the Ajax plumbing, but for page elements that you are interacting with. The page element objects have method to make this interact easier to program.

homepage: http://www.wassons.org

projectpage: http://prdownloads.sourceforge.net/pajaj/

• Ajax Coding Examples
  • Clone of Apple Demo
• Ajax Widgets
  • Ajax Tabs
  • Ajax MiniCalenar
  • Table Loader
  • GoogleMaps
• Other Widgets
  • Css Bargraph
  • CssVMenu
• Example Styled Elements
  • Slidebar
  • TabPanel
  • Rounded Section
  • PhpCode
  • Drop Shadow
  • Octopus Container
  • Button Bars

Google actually relies on our users to help with our marketing. We have a very high percentage of our users who often tell others about our search engine. — Sergey Brin

So spake one of the co-founders of Google. But what happens when your users start to tell others about your search engines in ways that you don’t like? When they present your search results in ways that hurt or confuse your brand? You would probably try to control how those users used those results. That seems to be what Google has done with the release of their new Google Ajax Search API.

Somewhat lost in the hype around the release of the Ajax API was the discontinuation of the Google SOAP Search API. It’s still available to existing subscribers, but no new ones are being signed up. To see why this discontinuation is an exercise in brand discipline, you just have to look at the terms of use for the Ajax API:

You agree that you will not, and you will not permit your users or other third parties to: (a) modify or replace the text, images, or other content of the Google Search Results, including by (i) changing the order in which the Google Search Results appear, (ii) intermixing Search Results from sources other than Google, or (iii) intermixing other content such that it appears to be part of the Google Search Results; or (b) modify, replace or otherwise disable the functioning of links to Google or third party websites provided in the Google Search Results.

The key terms here are that the order and appearance cannot be modified. And that is the essence of the Google brand: the order of the search terms. Fortunes are made and lost based on Google search position. Business plans are build around it. Millions of people around the world use the top ten results to find information, guide purchasing decisions, and so on. Mess with that order in some consistent way — in some, god forbid, way that people find valuable — and you’ve lost control of your brand, who you are, and likely your ability to advertise.

Now, with the new API, you can only use and display Google data inside a tightly circumscribed, parameterized boundary. Their order, their look and feel, their ads, their brand.

Of course there are many other ways of presenting search results. Many of the more interesting.ways to present the data reorder the results according to other criteria or third-party data (like other search results), or even dispense with a linear order. Now if you want to pull in search data and manipulate it in this way, you’re going to have to use the Yahoo! REST API’s. But will Yahoo! follow suit and get rid of their general API’s in favor of brand-preserving Ajax widgets? Dave Megginson doesn’t think so, but sees some clouds on the horizon.

Data APIs are not going to disappear, of course. AJAX widgets don’t allow mash-ups, and some sites have user bases including many developers who rely on being able to combine data from different sources (think CraigsList). However, the fact that Google has decided that there’s no value playing in the space will matter a lot to a lot of people. If you care about open data, this would be a good time to start thinking of credible business cases for companies to (continue) offer(ing) it.

I view this as a Hertz vs Avis opportunity for Yahoo! — “we try harder” with web services. Where Google might have been the first choice for many developers, now many will build the Yahoo! API’s into their applications and their frameworks. It takes just a few common plugins for packages like Drupal to boost market share.

The major changes are:

• Versioning: 0.12.2 to 2.2.0: The new version syncs up the internal and external release numbers
• Browser History Manager: The YUI Browser History Manager supports all A-grade browsers in managing the back/forward button navigation and bookmarking
• DataTable Control: The DataTable control allows you to present tabular data and allow your user to engage that presentation by modifying/enhancing the data, sorting and searching through it, and adjusting the presentation itself.
• Button Control: Buttons are essential parts of most graphical interfaces, but the visual constraints of buttons in their various form-control implementations (submit buttons, radio buttons, check boxes, etc.) diminish their effectiveness in some applications. The Button Control provides a platform for implementing visually impactful buttons that range from standard click-to-navigate buttons to radio buttons and checkboxes to advanced split-buttons that can operate as both a button and a menu.
• New YAHOO.* properties: such as YAHOO.lang, YAHOO.env, and a YAHOO_config global

Congrats on the new release.

download YUI Version 2.2.0 here

Ondrej Zara and his tem at Openlink Software have created a Openlink Software JS Toolkit, known as OAT. It is a full-blown JS framework, suitable for developing rich applications with special focus to data access.

OAT works standalone, offers vast number of widgets and has some rarely seen features, such as on-demand library loading (which reduces the total amount of downloaded JS code).

OAT is one of the first JS toolkits which show full OpenAjax Alliance conformance: see the appropriate wiki page and conformance test page.

There is a lot to see with this toolkit:

You can see some of the widgets in a Kitchen sink application

Sample data access applications:

• SQL Query By Example
• Forms designer
• DB Designer

OAT is Open Source and GPL’ed over at sourceforge and the team has recently managed to incorporate our OAT data access layer as a
module to dojo datastore.

source: ajaxian.com

The Problem

However, things are getting more complicated with AJAX. No page is loaded, but the content has changed. And it hasn’t changed instantly; AJAX is asynchronous by its definition. Setting a bug interval is a bad solution: it makes build cycle very slow without really solving the problem.

Some guys suggest using a “waitForCondition” command. In other word, every time AJAX is in action you need to manually add a waiting condition. This is much better then nothing; at least it is a real working solution. However, test creating is much longer and less fun.

Another option would be to extend Selenium to make it aware the underlying AJAX framework, so that the test case would pause until XMLHttpRequest is satisfied. Well, it requires extending Selenium, which is not very simple task neither. And there is a multitude of AJAX frameworks available, it would be impossible to adapt Selenium to every of them. And there are other in-browser testing solutions, not only selenium: both open source and commercial ones.

Solutions?

And the ideal scenario would be the following:

• Test, application itself or the in-browser testing framework raises a flag to mark the current session as the one of automated testing.
• AJAX framework detects the flag and passes to synchronous mode.
• In this case, a method of user action simulation (click/type) of Selenium will not return until the AJAX data is successful fetched and processed. So Selenium will not be able to continue before the page content is updated, and it’s exactly what the user expects from his macros.

source: ajaxian.com

• Cross-browser compatibility. Library works with IE5.0+, Mozilla 1.7+, FireFox 1.0+, Opera 7.3+, Safari (”+” means “in specified and newer versions”). By this token, code could work without ActiveX and XMLHttpRequest support (but if these capabilities are available, they are used automatically).
• File uploads from user browser to the server without page reloading.
• Full support of PHP debug features. If server-side script fails on an error (including fatal error, e.g., call of undefined function), client-side script can handle it correctly and show diagnostics. Besides response data, it is passed the output flow of server-side script which contains PHP error messages.
• Multi-dimensional data structures exchange (JSON analog) in client request and server response. At that, are used the standard PHP instruments — multi-dimensional associative arrays (request data available at $_REQUEST, response data may be saved to $_RESULT), as well as JavaScript standard capabilities — nested objects and properties. No XML in the level of API: you work with “native” language variables.
• PHP session support using usual way.
• Optimal data loading method choosing (XMLHttpRequest, Microsoft.XMLHTTP,
• Interface is compatible with XMLHttpRequest.

Downloads

• Client side JsHttpRequest.js
• Server side PHP JsHttpRequest.php

Prototype is a JavaScript Framework that aims to ease development of dynamic web applications.

Featuring a unique, easy-to-use toolkit for class-driven development and the nicest Ajax library around, Prototype is quickly becoming the codebase of choice for web application developers everywhere.

It is documentation Friday. The new site prototypejs.org has launched, and the call for documentation help rang through to some people.

This new documentation includes:

• Tips and Tutorials (e.g. Ajax, Extending the DOM)
• API Reference
• Blog