The official jQuery user interface library.
Go to file
2012-02-23 14:26:47 +01:00
build Build: Also minify i18n files. 2011-12-01 17:05:58 +01:00
demos Position: Fix initial positioning of cycler demo. 2012-02-23 14:26:47 +01:00
external Replace $.global with Globalize, update Spinner to use it. Related demos currently broken due to previous changes. 2011-08-10 14:55:16 +02:00
tests Menu: Clean up tests to remove nested setTimeout calls 2012-02-17 16:06:14 -06:00
themes/base Accordion: Simplify CSS so content panels never have a top border instead of toggling the bottom border of the headers. 2012-02-09 12:51:46 -05:00
ui Tooltip: Mark target to prevent async results showing a tooltip that was closed already 2012-02-19 21:29:41 +01:00
.gitignore Build: ant size will now give you a report detailing differences in size since the last time you ran the report 2011-10-17 14:37:36 -05:00
AUTHORS.txt Add Hans Hillen to AUTHORS.txt 2011-07-19 11:04:52 -04:00
GPL-LICENSE.txt removed extra level ui folder 2008-06-07 17:35:27 +00:00
jquery-1.7.1.js Upgrade jQuery to 1.7.1. 2011-11-22 08:43:09 -05:00
MIT-LICENSE.txt Updated copyright year. 2011-01-17 09:13:18 -05:00
README.md Readme: Add contributor instructions, for someone not looking at site or wiki first. 2011-07-15 21:00:37 -04:00
version.txt Updating the master version to 1.9pre. 2011-09-14 10:57:13 -04:00

jQuery UI - Interactions and Widgets for the web

jQuery UI provides interactions like Drag and Drop and widgets like Autocomplete, Tabs and Slider and makes these as easy to use as jQuery itself.

If you want to use jQuery UI, go to jqueryui.com to get started. Or visit the Using jQuery UI Forum for discussions and questions.

If you are interested in helping developing jQuery UI, you are in the right place. To discuss development with team members and the community, visit the Developing jQuery UI Forum.

For contributors

If you want to help and provide a patch for a bugfix or new feature, please take a few minutes and look at our Getting Involved guide, in particular check out the Coding standards and Commit Message Style Guide.

In general, fork the project, create a branch for a specific change and send a pull request for that branch. Don't mix unrelated changes. You can use the commit message as the description for the pull request.

For committers

When looking at pull requests, first check for proper commit messages.

Unless everything is fine and you can merge directly via GitHub's interface, fetch the remote first:

git remote add [username] [his-fork.git] -f

If you want just one commit and edit the commit message:

git cherry-pick -e [sha-of-commit]

If it should go to the stable brach, cherry-pick it to stable:

git checkout 1-8-stable
git cherry-pick -x [sha-of-commit]