The official jQuery user interface library.
Go to file
2011-07-27 15:41:38 +02:00
build Builds: used ant parallel task to run the two closure compiler steps and the yui css compressor step in parallel. The http get requests for documentation are also run in parallel. Reduced build time by about 40%. Fixed #7404 - build.xml can run quicker. 2011-05-20 21:17:30 +10:00
demos Merge branch 'master' into core-1.6.1 2011-07-25 11:53:14 -04:00
external QUnit update 2011-05-18 15:14:46 +02:00
tests Finish jquery-1.6.2 migration 2011-07-27 15:41:38 +02:00
themes/base Merge pull request #353 from kborchers/bug_7043 2011-06-16 10:35:04 -07:00
ui Merge remote branch 'kborchers/menu_home_end' 2011-07-25 23:57:51 +02:00
.gitignore Extend .gitignore with Eclipse WTP .settings 2011-07-12 10:06:49 -04: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.6.2.js Upgrade jQuery to 1.6.2. 2011-07-25 11:46:45 -04: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 2010-10-25 14:46:02 -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]