Monthly Archives: May 2010

Development | Releases

jQuery UI 1.9 Milestone 1 – Tooltip

Posted on by

The first milestone release for jQuery UI 1.9 is out, featuring the new Tooltip widget, in active development.

What’s a Milestone Release?

A milestone release makes it easier to try out the latest development code of jQuery UI without necessarily having to check out code from GitHub.

With a milestone release you can try out new widgets that are pretty far along (though not yet final) and provide feedback based on released code with a specific version number.

Note: the API is subject to change as the code is still under active development.

Tooltip

We’d love your feedback on our new Tooltip widget, to help ready it for the 1.9 final release. The API is already in good shape, so if you start using it now, migrating to 1.9 final should be really easy.

From the Tooltip documentation:

Tooltip replaces native tooltips, making them themable as well as allowing various customizations:

  • display other content than just the title, like inline footnotes or extra content retrieved via Ajax
  • customize the positioning, eg. to center the tooltip above elements
  • add extra classes to customize the appearance, for warning or error fields

A fade animation is used to show and hide the tooltip, making the appearance a bit more organic, compared to just toggling the visibility.

All you need is an element with a title attribute. Grab that element and call .tooltip() on it:

<a title="Details for this link" href="#">Link</a>
<script>
  $("a").tooltip();
</script>

When the mouse hovers over the element, the tooltip will appear, like so:

Demo: Forms with tooltips

Demos

Play with the latest demos in the tooltip branch on our live code view site, view.jqueryui.com:

Download

You can download the jQuery UI 1.9 Milestone 1 – Tooltip release as a zip file or via git:

File Downloads

Git

How to Provide Feedback

wiki page

To help with the design and development of the Tooltip widget, visit the Tooltip page on our Development & Planning wiki.

forum

If the comments section on the wiki page doesn’t provide enough room for your feedback, post to the Developing jQuery UI Forum and tag the post:

How to Contribute Code

If you have code changes for the Tooltip, fork jQuery UI on GitHub, commit to the tooltip branch, and submit a pull request.

If you’re new to git or GitHub, see our guide: How to submit a fix to jQuery UI – The Easy Way.

Comments

Note: please do NOT use the comments section of this blog post for feedback on the Tooltip widget. This discussion should occur on the wiki page and the forum (see How to Provide Feedback, above).

If you have feedback on us doing our first milestone release, feel free to leave a comment below. Thank you.

Development

How to submit a fix to jQuery UI – The Easy Way

Posted on by

Now that jQuery UI is hosted on GitHub, it’s even easier to start contributing fixes to the project.

Let’s walk through the easy way, where you don’t need to learn how to really use git. In another post, we’ll cover some best practices for contributing with git.

Let’s say you want to submit a patch to the Dialog file, jquery.ui.dialog.js.

Step 1: Sign up for GitHub (jump on it)

Step 2: Fork the jQuery UI repository (become a committer of your very own copy of jQuery UI)

Step 3: Modify your fork through the GitHub web interface (commit your change without knowing git)

  • http://github.com/{your-username}/jquery-ui
  • Click on the folder and file you want to modify
    • click “ui/”
    • click “jquery.ui.dialog.js”
  • When you’re viewing the contents of the file you want to change, click the “edit” link (top right)
  • Make changes to the file in the editor
  • Enter a Commit Message to summarize the changes you’ve made and why you’ve made them.
    • This should include a reference to a Trac ticket, formatted like so
    • “Dialog: modified the foo to no longer bar. Fixed #1234 – dialog: IE6 crashed when foo is set to bar”
    • Be sure your commit message includes 4 parts: the WHERE, the WHAT, the WHY #Num, and the WHY Name. See the jQuery UI Commit Message Style Guide for more detail.
  • Click “Commit”

Step 4: Submit a Pull Request (tell the jQuery UI team why your change rocks)

  • http://github.com/{your-username}/jquery-ui/blob/{id-of-commit}/ui/jquery.ui.dialog.js
  • Click “Pull Request”
  • Enter a Message that will go with your commit to be reviewed by core committers
  • Click “Send Pull Request”

Step 5: Add a link to your commit to the ticket in Trac (tell everyone you’re on the case)

Step 6: Eat a cookie (yum)

  • You’re done!

Now if you need to change multiple files as part of one commit, the web interface will not be the way to go. In that case you’ll want to learn a little more about GitHub and git. You can start here:

Releases

jQuery UI 1.8.1

Posted on by

The first maintenance release for jQuery UI 1.8 is out. This update brings a bunch of fixes to Autocomplete and a few fixes to other plugins. For the full list of changes, see the changelog. You can download it here:

Download

File Downloads

Svn (contains final files as they are in the zip, with @VERSION replaced with 1.8.1, all themes)

Git (contains pre-build files, with @VERSION not yet replaced with 1.8.1, base theme only)

Google Ajax Libraries API (CDN)

Custom Download Builder

Changelog

See the 1.8.1 Changelog for full details on what’s included in this release.

Thanks

Thanks to all who helped with this release, specifically: andyurivecchi, AzaToth, jeresig, jzaefferer, misterakko, nigel, paul.irish, rdworth, Rwhitbeck, scott.gonzalez, scottjehl, and wewals.

Releases

jQuery UI 1.7.3

Posted on by

The third maintenance release for jQuery UI 1.7 is out. This is an update to the legacy 1.7 to make it compatible with the latest jQuery 1.4, in case you aren’t yet able to upgrade to the latest jQuery UI 1.8. You can download it here:

Download

File Downloads

Svn

Google Ajax Libraries API

Custom Download Builder

Changelog

See the 1.7.3 Changelog for full details on what’s included in this release.

Thanks

A huge thanks to Scott González for making the changes required for this release.