Welcome to the jQuery UI design & planning wiki
This is a public wiki to plan, design, document, and discuss the future of jQuery UI plugins, and theming support. This is not the jQuery UI documentation. Please feel free to contribute your ideas.
Learn more: vision and goals, team, plugin priortization process, development phases, wiki language styleguide, how to submit your plugin for inclusion.
Status summary
We're working on the 1.6rc3 release. This release includes major and minor fixes and updates to each 1.5 component as well as two major updates:
This 1.6rc3 release will be ready as soon as the following tasks are completed:
- progressbar refactored - design (100%), specs (100%), development (90%), testing (90%), documentation (0%)
- all blockers fixed (13 open, http://tinyurl.com/ui1-6blockers)
- all new tickets triaged (64 open, http://tinyurl.com/ui-triage)
- all plugin docs updated - at a mininum: options, defaults, callbacks, ui parameter, methods
- sufficient unit test coverage for all plugins. Shooting for 30-40% overall with no individual plugin less than 30% (currently about 15% overall)
- re-vamped jQuery UI CSS Framework finalized, implemented, and tested for all plugins in all supported browsers
- new ThemeRoller app design and improved theme gallery
- particularly hideous demos (on the ui site) should be touched up to use the new Themeroller styles at the very minimum. Major demo rework will be post-1.6
The 1.6 final release will follow after a sufficient testing period (and assuming rc4 is not warranted), but with the additional requirements:
- all blockers and criticals fixed (15 open)
- documentation should include at least one live demo for each plugin. Ideally one demo for each option.
- unit test coverage should be greater than 1.6rc3. Shooting for 40-60% with no individual plugin less than 40%
The next major release (aka 1.next) is 1.7 and candidates for inclusion are highest priority plugins currently in the dev branch
as well as any dependant utilities:
Maintenance 1.6 releases (1.6.1, 1.6.2, etc.) will be developed in branches, not in the trunk. After the 1.6 release is finalized, the trunk will change to version 1.7pre. No plugin will be moved from the dev branch to the trunk until it meets the same level of readiness as demonstrated by 1.6final, in terms of design, specs, development, testing, documentation, and demos. This is true of major refactorings (of existing components) as well. They should be done in a dev branch, leaving the previous version in the trunk until the refactor is complete.
Full list of plugins planned for jQuery UI
You can sort this table by clicking on the table header for each column. Each page uses this widget template.
Learn from other's UI mistakes: check out the UI hall of shame.
Comments (0)
You don't have permission to comment on this page.