The Road to 1.0

Posted on by

I wanted to give everyone an update as to the progress that’s been made (and being made) on jQuery right now. A bunch of us have been working very hard on getting jQuery squared away for a proper 1.0 release. In order to achieve this goal, I wanted a couple things done:

  1. Cutting down the size. I want jQuery no larger than 15k – as of right now, the code in SVN is sitting at a nice 14.8k (or so).
  2. Speed ups. Some very important speed ups are going into place, including caching and object-oriented code.
  3. Stability. I want jQuery 1.0 to be a solid release that will be supported for a very long time.
  4. Excellent documentation. We’ve been working on getting the new jQuery Wiki squared away. It’s release, along with brand new documentation, will be released at the same time as the 1.0 release.

The game plan is to have a copy of 1.0 out by the end of the month (probably a beta). Right now, the biggest thing left is to write are lots and lots of test cases to make sure that everything is running smoothly. If you’d like to help with test cases, or with the documentation efforts, please comment on this post or post in the mailing list.

This is going to be a great release – I’m really excited about the quality of code that’s coming out of it, and I’m sure you will be too.

10 thoughts on “The Road to 1.0

  1. Andrea on said:

    Hi John – that’s great news.

    I’ve been busy in the past months and haven’t been able to keep up with the hundreds of emails in the mailing list, so the blog is currently my only true source of information on your progress. It’s great to see that jQuery has enjoyed such a big success among web developers at many levels.

    I had a look at my (small) series of test, and found that one of them still fails: the ‘not’
    Tests with IE and Fx fail on the last assert both with the production and the dev/sane versions.

    Also, I wrote a new test after hitting a problem, in the dev/sane version, with attribute selectors (which made my test page fail on that lib):
    Here behaviours differ slightly between IE and Fx:
    Both Fx and IE – production:
    2: (elements with any attribute – finds none)
    Both Fx and IE – dev/sane:
    4: (match keyword in space separated list)
    9: (substring of attribute)
    Only IE – dev/sane:
    2: (but not same error: finds too many!)

    I hope this helps,

  2. Sounds good!, jQuery is on top for me list of must have.

    here is what i just did with it, that is very common and should makes its way into the Documents. its the old Get set of checkbox’s by class name and do something with them.. same method can be used for say advance stuff too, something like Saving the Drag and Drop Sort list as in LI tags, drag and drop yah i know web2.0 yay! but back to my point at hand… jQuery makes my life easy to code , here is a sample of how to grab list of checkbox or list of LI and return the order.

    image another
    image one more
    image one more last

    var SORT_TN = {	
      OFF_SET : 1,
      GRAB_IDS : function(){
        var tx = '';
        var IMGS = $2("li.TN_IMG").each(function(i){
          i = SORT_TN.OFF_SET+i;
          tx += + "=" + i + ","; 
        // this is my test results for saving the sort ids's ,
        // above code is clean cut!

    NOTE: OFF_SET is if you want to change the start number, else it can be removed from above example, then the start number will be 0

    test it by run:


    results in something like 83=1,85=2,58=4,38=5 etc.. meaning the ID numbers are 83, 85 etc.. and sort number match up that need to be saved into database or whatever you are doing.

    I use the above method to Sort Thumbnails in a gallery and save the sorted new thumbnails in database and refresh! very hot! hot hot!

  3. Your progress looks fantastically quick and productive. I’m a recent convert to jQuery, but I hope I could be useful writing docs or tests. Please let me know if you need help.

  4. I’ve been using other JS frameworks and recently tried to used JQuery and it didn’t dissapoint. It’s great. Let me know how I can help in the testing or documentation.

  5. wesley on said:

    I had hoped you could reach that 10kb again :(

    Maybe you should extract the xpath functions in a plugin.

    Good work anyway :)

  6. moyun on said:

    > Right now, the biggest thing left is to write **are** lots and lots of test cases to make sure that everything is running smoothly.

    Is the word “are” necesssary?