The official jQuery user interface library.
Go to file
2012-05-14 11:49:44 +02:00
build Build: Modify uglify.js to include a newline charakter after the copyright comment, makes diffing against new build a little bit more efficient 2012-03-10 14:16:13 +01:00
demos Merge branch 'master' into selectmenu 2012-05-14 11:49:44 +02:00
external Update QUnit. 2012-03-21 13:24:31 -04:00
tests Merge branch 'master' into selectmenu 2012-05-14 11:49:44 +02:00
themes/base Merge branch 'master' into selectmenu 2012-05-14 11:49:44 +02:00
ui Merge branch 'master' into selectmenu 2012-05-14 11:49:44 +02:00
.gitignore First iteration on grunt-based build. lint, qunit, concat, min and zip all work, but all have various limiations. 2012-03-02 16:45:10 +01: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
grunt.js Grunt: Removed newcap option from jshint task. 2012-04-02 22:20:18 -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 Build/grunt: Fix dependencies to versions we've tested against. No more surprise API changes, for now 2012-04-02 15:59:32 +02: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 Bump version 2012-03-28 18:50:57 +02: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]