Web Info & Tutorials

Following a very successful release of jQuery v1.2, the jQuery team has just announced the release of their new UI & effects library, jQuery UI.

jQuery UI signals the start of a whole new branch of the jQuery project which will focus on developing high-quality, reusable, components that you’ll be able to drop in your applications. Frequently, these components are coming directly to you from traditional jQuery plugins, but with strict coding, documentation, themeing, and demo standards. We hope you’ll enjoy this new level of quality as much as we do.

The jQuery UI library was a natural extension to the jQuery project and the team was anxious to provide a rich set of UI controls that could be used to build highly interactive web applications. The library runs the gamut of functionality expected in a UI resource by including:

Mouse interactions:

• Draggables
• Droppables
• Sortables
• Selectables
• Resizables

Interactive Widgets:

• Accordions
• Date Pickers
• Modal Dialogs
• Sliders
• Table sorters
• Tabs

Effects:

• Shadows
• Magnifier

In addition, the jQuery UI team took the extra steps to allow controls to be themed, thus allowing developers to create their own look-and-feel for components:

We’re launching with one complete theme: Flora (designed by Tom) and two partially-complete themes: Light and Dark (by Sean). Within the next week we’re going to be announcing the details of a new theming competition, along with everything that you need to completely build your own jQuery UI theme.

A complete, detailed explanation of the features of jQuery UI can be found on the jQuery blog as well as the new jQuery UI home page.

Note: jQuery UI requires that you use, at least, jQuery 1.2.1 or newer.

One of the enduring criticisms of ZK, the server-side Ajax framework, has been against its perceived slow performance. Critics have observed, and supporters have conceded, that applications written with ZK seem a touch slow. So it’s no surprise that a major focus of the latest major release has been improved performance. The ZK team found two major bottlenecks in performance testing:

After a series of stress test and reviewing the kernel code, we found out 2 bottlenecks on ZK 2.4.1 and fixed them in ZK 3.0 RC.

1. The executing time is too expensive when rendering components. ZK uses templates to render components, and the EL is generally used in templates to simplify the variable access and templete maintenance. However, when the concurrent access rises to a large number, the overhead on rendering component with EL is too heavy.
2. Threads spend too much time on waiting the synchronization when many threads access to the same cache under current cache mechanism.

ZK 3.0 RC solves these 2 bottlenecks by using the renderer class and new cache mechanism. The test result shows ZK 3.0 RC is four ~ five times faster than ZK 2.4.1.

I haven’t validated these performance figures myself, but an initial comparison between some demo applications confirms a much more responsive user experience.

ZK 3.0 RC has also added a number of other new features:

• Server push is enabled which allows you to update client’s information actively and the usage is simple and intuitive.
• Add forward property of components to forward event without programming.
• New expression of annotation is ease of use, and easy-to-read.
• TreeModel is introduced which simplifies the job of Tree rendering.
• Flash components allow you to play audio and video files. (including youtube clip)
• Native namespace is implemented to speed up the performance while integration with HTML.
• To speed up the performance of ZK, EL evaluator is pluggable, and a new way to render ZK components is introduced.
• More integration with other frameworks, ZK has integrated with JSF, JSP, and Ext-JS.

Server push was already supported in ZK through use of the timer component, but the enhancements make it even easier (note: we’re not talking comet, but rather client polling). Even more exciting for me is the dynamic loading of ZUML (the XML-based markup language for specifying ZK interfaces) pages dynamically from sources such as a database. That’s very helpful if you want to allow non-developers to deploy interface changes without having to spit out ear or war files.

As usual, the ZK folks have done a good job documenting the changes and additions. It’s too early to tell if 3.0 will solve all of ZK’s previous shortcomings, but ZK is well on it’s way to becoming my favorite server-side framework.

Douglas Crockford micro-blogged it best:

I hit been at character for digit years. One of the prototypal things I did when I got there was to do a View Source of the face page. That gave me a aggregation of saliency into how things were done. I also saw whatever things to improve. That inspired me to indite the prototypal digit chapters of The Elements of JavaScript Style. Part One. Part Two.

He explains finished example, the following:

• Avoid early constructions.
• Always ingest blocks in organic statements.
• Avoid naming expressions.
• Use goal augmentation.
• Use ordinary libraries.
• Watch discover for identify causation when using ==.
• Use the ?: cause to superior digit of digit values.
• Never ingest inherent orbicular variables.
• Do not ingest the ?: cause to superior digit of digit actions.
• Use the || cause to take a choice value.
• Global variables are evil.
• Use intrinsic functions to refrain orbicular variables.

What’s your style?