Version 1.0.X. Changes and fixes in 1.0.1. and 1.0.2.
Version 1.0.2. June 11, 2009
The power of combinations
jQuery Tools can be easily combined. This gives you a lot of new possibilities for experimentation and new widgets that are based on multiple tools working together. We have a new demo called An artist's portfolio which uses two scrollables, an overlay, tooltips and an exposing effect. It also uses one jQuery plugin that does not belong to the library. These tools can obviously be used together with other libraries and tools out there.
cdn.jquerytools.org is now gzipped
The official Tools distribution is now gzipped:
I had a true mess with various DNS, CDN and CNAME configurations. Now I almost understand how these work. :P
Minor changes and fixes
- expose: Now works with elements whose position is static (fixed), see forum post.
- overlay: When being used with the mask property the close action sometimes fails. This has been fixed.
- overlay: Multiple initializations to the same overlay element (with target property) caused multiple close buttons to be created. This has been fixed.
- scrollable: Using a zero (0) in the scrolling animation caused it to use the default speed (400ms). Now zero speed is possible (no delay between changing panes).
- scrollable: When autoScroll was enabled and it was programmatically paused, this caused multiple timers to be created. This was spotted in this thread. autoScroll is now considered a deprecated feature and it will be replaced by an "autoscroll plugin" in scrollable 1.2.
- tooltip: Fixed a bug where the trigger could change when it had child elements, such as table. See this forum thread.
- tooltip: The tooltip now closes when the mouse leaves the tip while it's still being animated. See this forum thread.
- tooltip: New built-in effect: "fade" with two configuration variables: fadeInSpeed and fadeOutSpeed.
- tabs: Added the new method getConf() that returns the tab configuration.
- tabs: Added a new configuration option, fadeInSpeed, that can be used together with the built-in "fade" effect. This property defines how fast the opened pane reveals itself. Suggested by "paradise" in this thread.
Version 1.0.1. June 07, 2009
jQuery Tools vs jQuery UI
The initial release was an unexpected success. Before the release, there were around 60 000 page loads/day on the Flowplayer website and two days after the release there were 270 000 page loads! On Twitter, a search for jQuery Tools will give you thousands of highly positive responses. At one point, there was a new Tools related status update occurring every two minutes. The slogan "Missing UI library for the Web" seems to be true.
I am glad to say that the Tools are really stable and so far only 4 bugs have been found and they have all been fixed in this release.
A major change in tooltip
The biggest "semantic" bug was in tooltips and I needed to change the way it was being initialized. In 1.0.0 you had to do following:
This did not match the philosophy behind jQuery: 1. Find element(s) on the page and 2. Do something to them. Because the tooltip is a behavior and not its own entity, we need to grab elements on the page and attach tooltips to them. In tooltip 1.0.1. the initialization goes like this:
Now, instead of selecting the tooltip, we are selecting the triggering element. So, if you have already using the tooltips, you'll need to change your setup a little bit. Sorry for the inconvenience. Look at the minimal setup for tooltip for more details.
jQuery Tools vs jQuery UI
The above bug was a starting point to an article that compared jQuery Tools and jQuery UI. This article became a bit flamy and more and more people (including me) started to comment on it. I recommend reading the article and the comments: jQuery Tools vs jQuery UI.
The article also criticizes the API of jQuery Tools. In response to this, I have rewritten the API documentation which is now more clear. You can see that there is even a jQuery UI compatible way of using the Tools API which has been there from the beginning. It has now been opened to the public. Notice also that the User's Guide has a new section: using the Tools with other plugins and libraries.
Now both issues in the article: the tooltip semantics and "going solo with the API" have been resolved.
Minor changes and fixes
- scrollable. Fixed a bug where the Alt-left and Alt-right browser keystrokes failed to navigate backwards and forwards between pages. Now, when the Alt or Control keys are pressed, the arrow keypresses are ignored. See the details in this forum thread.
- overlay. The load method can now be called upon $(document).ready(). See the details in this forum thread.
- tooltip. tooltips now work corretcly with textareas. See details in this forum thread.
- tooltip. the tooltip can be positioned next to the trigger element's parent too. This is sometimes needed in forms, for example. The input is nested inside a label element and the tooltip is placed next to the label. See the details in this forum thread.