Confirmed users, Bureaucrats and Sysops emeriti
1,531
edits
Jetpack/Design Guidelines: Difference between revisions
no edit summary
ChrisHofmann (talk | contribs) No edit summary |
ChrisHofmann (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
* <strike>Generative</strike> | * <strike>Generative</strike> | ||
* The Jetpack APIs and development system for extending the browser will be made as simple as possible, as easy to learn, and as easy to maintain as possbile | * The Jetpack APIs and development system for extending the browser will be made as simple as possible, as easy to learn, and as easy to maintain as possbile | ||
** Clear and consistent APIs -- guidelines will outline naming conventions (CamelCase?), placement and position of arguments (jquery like? options, arg, callbacks?) | ** Clear and consistent APIs -- guidelines will outline naming conventions (CamelCase naming, etc..?), placement and position of arguments (jquery like? options, arg, callbacks?) | ||
** Minimal API Set -- Make sure we have solid use cases for each API and have reduced to common root. | ** Minimal API Set -- Make sure we have solid use cases for each API and have reduced to common root. | ||
** Complete, Comprehensive & Orthogonal APIs across the full API set - find all the common attributes/arguments (add, remove, get, set) make a grid and make sure its complete. | ** Complete, Comprehensive & Orthogonal APIs across the full API set - find all the common attributes/arguments (add, remove, get, set) make a grid and make sure its complete. | ||