Web Info & Tutorials

September 11th, 2007

JQUERY V1.2: MAJOR NEW RELEASE, SNEAK PEAK AT JQUERY UI

Hot on the heels of the jQuery v1.1.4 release, John Resig and the jQuery team put the pedal to the metal and announced their newest release, jQuery v1.2.

This is a massive new release of jQuery that’s been a long time in the making - and it’s ready for your consumption!

This release is feature packed adding such new features as:

Following the tradition of “playing nice with other libraries”, jQuery v1.2 now provides the ability to define a custom namespace for the events expando, thus adding one more method of ensuring that jQuery developers can successfully work in a multi-library environment. John Resig had this to say:

It’s incredibly important for us, and our users, that the jQuery library work in any JavaScript environment. In jQuery 1.2 you can now depend on the fact that jQuery will protect itself from outside code influences, and libraries, even going so far as to protect itself from other versions of jQuery that might be running on the same page. Knowing that your copy of jQuery will always behave the way you expect it, no matter what the platform, is the cornerstone of the project.

Along those same lines of working for the community, the team has provided jQuery developers with an easy way to migrate into jQuery v1.2 by providing a compatibility plugin. With some functionality being removed in jQuery v1.2 release, including this plugin allows developers to have all of the features that were removed in the newest release.

The full release notes provide details about all of these new features.

You can get the latest release of JQuery below:

jQuery 1.2: (How To Upgrade)

Plugins:

As if a new major release wasn’t enough to whet your appetite, on Sunday, September 16th, the new jQuery UI effects library will be released to the public. The library will include:

  • Draggables
  • Droppables
  • Resizables
  • Shadows
  • Sliders
  • Sortables
  • Tabs
  • Accordions
  • Selectables
  • Trees
  • Modals

All completely documented, demoed, themed, and 100% Free Open Source Software.

Here’s a sneak peak at what to expect:

Lead developer of jQuery UI, Paul Bakaus, had this to say:

We worked hard over the last three months to make UI a seamless, rock-solid solution for many interface situations. It’s nearly there - featuring many core level modules, ready-to-go widgets and custom, unique themes. To make the experience even nicer, the team created a smart downloader, a playground with demo apps and tests and of course documentation. We are pretty excited about our release on Sunday - be sure not to miss it!

September 11th, 2007

MAKING OFFLINE WEB APPLICATIONS EVEN SIMPLER:

Ian Hickson has been doing a great job defining how web pages can declare themselves as applications, and can thus work offline.

He has seen that there is a common case, which is “When you build a true web application, many people do so via the single page model”. If you take this assumption, wouldn’t it be nice to tag the top page as an application, and have the browser subsystem take care of caching files and using them correctly when offline. His assumption is based on the logic that: “If you have complicated server logic you use a multiple page application, which isn’t going to do much in an offline mode anyway, as it has complicated server logic!”.

Some people do not subscribe to this view, and think that there is a lot of multiple page applications that can be made to be web enabled, and so his latest thoughts take that into consideration.

The idea is that you can then <html application=”manifest-of-urls.txt”> and use a different path. He starts with:

Ok, new proposal:

There’s a concept of an application cache. An application cache is a group
of resources, the group being identified by a URI (which typically happens
to resolve to a manifest). Resources in a cache are either top-level or
not; top-level resources are those that are HTML or XML and when parsed
with scripting disabled have with the value of
the attribute pointing to the same URI as identifies the cache.

When you visit a page you first check to see if you have that page in a
cache as a known top-level page.

If you do, skip the next two paragraphs; the ‘new cache’ flag is set to
false.

…. and the logic keeps going ….

Seeing simpler and simpler offline support is great.

September 11th, 2007

SYBASE SHOWS AUTO CHANGE TRACKING AND SYNCING WITH GOOGLE GEARS AND IANYWHERE

Eric Farrar of Sybase iAnywhere has been developing a prototype that allows direct database-to-database synchronization of a Gears application to Oracle, SQL Server, DB2 and Sybase databases. We asked Eric about his work and he told us:

At Sybase iAnywhere we provide a data sync infrastructure for mobile and remote apps. The Background Sync architecture mentioned on the Gears site is a lot like mobile application architectures we see all the time. As a result, it seems as though the same mobile sync technology can be used to solve the offline sync problem for Google Gears.

This prototype uses a local lightweight database (based on the iAnywhere UltraLite database) with built-in synchronization
capabilities, meaning:

  • Built in change tracking, so that changes (including deletes and updates) can be sent to the server,
  • Built in state tracking, so that the local database knows when synchronizations succeed and can take appropriate clean-up operations automatically,
  • Built in synchronization over TCP/IP or HTTP.
  • Optional encryption of the data store and of the sync stream
  • Somewhat stricter data management model than SQLite.

The other piece is the sync server that manages synchronization to Oracle, SQL Server, IBM DB2 and Sybase databases. The sync technology is fully transactional, meaning data does not get partially changed at either end. It also has automatic mechanisms to detect conflicts and hooks that allow users to programmatically handle the conflicts using SQL, .NET, or Java.

As far as scalability, these technologies are currently being used in projects that involve nearly half a million mobile devices.

Eric also recorded some videos show this all in action:

Google Gears Prototype with Auto Change Tracking and Syncing (3 min 13 sec)


Prototype of Google Gears Database Syncing with Oracle (3 min 16 sec):


September 11th, 2007

QOOXDOO TECH TALK PRESENTATION

The prototypal of our transcribed sessions from The Ajax Experience (East shore coming!) is today live.

You crapper view the presentation on qooxdoo, with Andreas Ecker, Project Lead of qooxdoo and Derrell Lipman, qooxdoo Team Member.

qooxdoo is a broad and original Open Source JavaScript framework. In this session, you’ll wager how to investment qooxdoo to amend professed JavaScript applications, using its state-of-the-art interface toolkit that allows for cushy utilization of awesome cross-browser scheme applications. Project advance Andreas Ecker and aggroup member Derrell Lipman module also shew and handle qooxdoo’s foppish Ajax and far machine call act layers.

In this session, you module wager how to:

  • Use qooxdoo’s panoramic clothing of widgets and its agency concern to easily amend genuinely original scheme applications;
  • Create applications with zero-footprint and no module leaks;
  • Have your covering separate transparently to the user;
  • Build applications without some noesis of CSS or modify HTML, using exemplary commands from another field toolkits for autochthonous applications.

Once you start the show window, you module wager a flooded transcript that you crapper peruse.