Go check out the release notes.

Related posts:

1. jQuery 1.4 Released
2. jQuery 1.3.1 Go For Launch
3. jQuery 1.4 Alpha 1 Released

View the release notes here: http://jquery14.com/day-01/jquery-14

Related posts:

1. jQuery 1.4.2 Released
2. jQuery 1.4 Alpha 1 Released
3. jQuery 1.4a2 (Alpha 2) Released

1.4 is slated for official launch on January 14th - how cute :)

Related posts:

1. jQuery 1.4 Alpha 1 Released
2. jQuery 1.3 Beta Testing
3. jQuery 1.4.2 Released

Most of the changes seem to revolve around heavy optimization of some core functionality. Installing this alpha and testing in live applications will help get this release out!

Related posts:

1. jQuery 1.4a2 (Alpha 2) Released
2. jQuery 1.4.2 Released
3. jQuery 1.4 Released

I waited for the 1.3.1 release of jQuery to make sure all major bugs had been resolved (brand new selector engine). This weekend I decided to go for the upgrade. Flawless. Even the plugins all worked as expected.

Fantastic job.

Related posts:

1. jQuery 1.3 Beta Testing
2. jQuery 1.4.2 Released
3. jQuery 1.4 Alpha 1 Released

Major changes include:

• Selector Engine - The selector code has undergone a complete rewrite - it’s likely that some edge cases still exist here.
• DOM Manipulation (append/prepend/before/after) - This code has also undergone a large rewrite along with some of the logic for executing inline script elements.
• .offset() - Another method that has been completely rewritten.
• Event Namespaces - The logic for handling namespaced events has been completely rewritten.
• Event Triggering - When triggering an event the event now bubbles up the DOM - this is likely to cause some problems.

Go lend a hand!

Related posts:

1. Converting from Prototype to jQuery
2. jQuery 1.3.1 Go For Launch
3. jQuery 1.4.2 Released

Over the years of being a Prototype user I paid close attention to the many posts about why X is a better framework than Y. I had always planned on at least TRYING another framework at some point to see what all the fuss was about.

Initially what attracted me to jQuery was it's compactness. It doesn't have separately defined classes for each component, like Prototype. There's one point of entry and most everything revolves around DOM elements. There's no distinction between selecting a single or multiple DOM element(s) and, because jQuery only uses a selector syntax, you don't get confused whether the parameter passed is an ID, class, etc.

Furthermore, I never really liked having to use $ for single selection and $$ for multiple selections in Prototype. Relatively speaking, with jQuery I find that performing actions on multiple DOM elements is easier.

Chaining is really where jQuery shines. It reminds me of using the 'with' construct in Visual Basic back in the day. "This is the object that I want to perform actions on... do this, that, and this... thanks!".

However, unlike Prototype where one could test for the existence of an object by:

if($('objectID')) {
// do something
}

In jQuery it isn't quite so intuitive. Since all jQuery instances are collections of elements, you test for the existence of an element by checking its length property:

if(jQuery('#objectId').length == 1) {
// do something
}

In jQuery, binding to events is also very intuitive. Combined with the power of chaining adding event handling to multiple objects is ridiculously simple. And, because the code executed in your event callback has the context of the object that triggered the event, you can (more easily than bindAsEventListener in Prototype) just access the object within the callback via 'this'.

This brings me to one issue that did initially cause some conversion conflict. Prototype does a good job of automatically extending standard objects, objects returned, and parameters passed. With jQuery, you have to get used to 'get()'ing the root DOM element if you need to manipulate it and likewise, extending a root DOM element to a full fledged jQuery instance (such as 'jQuery(this)') if you want to manipulate it via jQuery.

Another primary reason why I switched to jQuery is because it has built in support for basic animations. Transitional animations give that extra something to a web app. Having to hand-code them isn't pleasant. Obviously Prototype has scriptaculous, but thats a huge size (and therefor performance) commitment to make for just a simple fade, no?

jQuery was built to be extensible. It seems to me that Prototype intended to be the "be all, end all" solution to your JavaScript woes. jQuery takes a more sensible approach - it provides the fundamental structure and handles the most-desired scenarios. If there's something it doesn't do out of the box there's probably a plugin available that does. Most likely someone has come across the same shortcoming already and written a plugin to fulfill the need.

Some plugins I ended up needing immediately were:

• Date picker
• CSS Extraction from Ajax responses (IE issue)
• Ancestry (to mimic Prototype's descendantOf())
• DOM element creation (to mimic the functionality of Prototype's Element class)

I prefer to create DOM elements in JavaScript programatically without using HTML. jQuery doesn't have a built in solution for creating DOM elements like Prototype does with its Element class. Fortunately, Lukasz Rajchel has written the DOMEC (DOM Element Creation) plugin. It's lightweight and is a drop-in replacement for those familiar with the syntax of Prototype's Element.

During the conversion process I found it to be most helpful to load jQuery side by side with Prototype using jQuery's no-conflict functionality. As I slowly combed through my JavaScript removing Prototype dependencies I would periodically remove Prototype to see if and where I missed any outliers. This also requires you to use the jQuery() syntax as opposed to the traditional $() syntax. In doing so this helps easily identify where Prototype code remains.

How have your conversions to jQuery gone? Have you converted and never looked back? Your thoughts are appreciated...

Related posts:

1. jQuery 1.3 Beta Testing
2. JavaScript Event Handler
3. jQuery 1.4 Released