Welcome to the jQuery UI design & planning wiki
This wiki is used to document and discuss the user interface patterns associated with jQuery UI utilities, widgets, and theming support. This is not jquery UI documentation. Please feel free to add to these pages, we welcome your input and ideas. This wiki is public to view and comment, so feel free to link to pages. Our vision and goals
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:
- new plugin: progressbar (see progress indicator)
- re-vamped ThemeRoller class structure that includes a new rounded corner class and improved icon set
This release will be ready as soon as the following tasks are completed:
- progressbar refactored - design (80%), specs (0%), development (0%), testing (0%), documentation (0%)
- all blockers fixed (8 open, http://tinyurl.com/ui1-6blockers)
- all new tickets triaged (83 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 ThemeRoller framework finalized, implemented, and tested for all plugins
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 (11 open)
- documentation should include at least one live demo for each plugin. Ideally one demo for each option.
- 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
- 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 a branch, 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.
Utilities & Widgets
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.