Jetpack/Design Guidelines: Difference between revisions

Jetpack/Design Guidelines (view source)

3 bytes added , 3 February 2010

no edit summary

Confirmed users, Bureaucrats and Sysops emeriti

1,531

edits

@@ Line 1: / Line 1: @@
 Jetpack APIs and features provided are intended to improve the following areas of Firefox extensibility
@@ Line 9: / Line 8: @@
 * 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 consistant APIs -- guidelines will outline naming conventions (CamelCase?), placement and position of arguments (jquery = options, arg, callbacks?)
+** Clear and consistant APIs -- guidelines will outline naming conventions (CamelCase?), placement and position of arguments (jquery like? options, arg, callbacks?)
 ** Minimal API set (make sure we have use case).  reduce to common root
@@ Line 19: / Line 18: @@
 ** error handling.
-** testing -- APIs will be created in testdriven development process.  write the tezt first, then develop support for the api to pass the test.
+** testing -- APIs will be created in testdriven development process.  write the test first, then develop support for the api to pass the test.
 ** extensibility.  The goals list above all strive to keep the base set of supported APIs as minimal as possible, and then allow extensibility for creating additional experimental features.