The official jQuery user interface library.
Go to file
2012-05-15 16:10:12 -04:00
build Build: Removed ant build. 2012-04-18 16:31:30 -04:00
demos Autocomplete combobox demo: Add combobox-specific classes for styling. Fixes #8322 - Autocomplete: Combobox demo should not override .ui-button styles. 2012-05-14 21:38:30 -04:00
external Update to QUnit 1.6.0 2012-05-04 12:24:32 +02:00
tests Removed static tests directory. 2012-05-15 16:10:12 -04:00
themes/base Merge branch 'master' into position-notification 2012-04-20 11:06:11 -04:00
ui Tabs: Replaced fx option with show and hide options. Fixes #8319 - Tabs: Deprecate fx option. 2012-05-14 14:40:06 -04:00
.editorconfig Add EditorConfig file denoting indentation for JS 2012-05-15 13:41:15 -04:00
.gitignore Build: Removed ant build. 2012-04-18 16:31:30 -04:00
.jshintrc Use .jshintrc files. 2012-04-20 11:19:27 -04:00
AUTHORS.txt Updated authors list. 2012-05-14 11:26:51 -04:00
GPL-LICENSE.txt removed extra level ui folder 2008-06-07 17:35:27 +00:00
grunt.js Grunt: Added task for generating the list of authors. 2012-05-14 17:19:10 -04:00
jquery-1.7.2.js Upgrade jQuery to 1.7.2. 2012-03-22 09:45:22 -04:00
MIT-LICENSE.txt Updated copyright year. 2012-03-08 10:53:08 -05:00
package.json Update node-testswarm to 0.2.2 2012-05-07 11:52:17 +02:00
README.md Updated readme. 2012-05-15 14:12:50 -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 develop jQuery UI, you are in the right place. To discuss development with team members and the community, visit the Developing jQuery UI Forum or in #jquery on irc.freednode.net.

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.

Do not merge pull requests directly through GitHub's interface.

Fetch the remote first:

git fetch [their-fork.git] [their-branch]

Then cherry-pick the commit(s):

git cherry-pick [sha-of-commit]

If you need to edit the commit message:

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

If you need to edit the changes:

git cherry-pick -n [sha-of-commit]
# make changes
git commit --author="[author-name-and-email]"

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-from-master]

NOTE: Do not cherry-pick into 1-8-stable until you have pushed the commit from master upstream.