Labs/Jetpack/Reboot/Best Practices: Difference between revisions
Jump to navigation
Jump to search
(Oops, typo) |
(added more TODOs) |
||
| Line 2: | Line 2: | ||
* See [[Labs/Jetpack/Reboot/Style_Guide]] for coding style guidelines/discussion. | * See [[Labs/Jetpack/Reboot/Style_Guide]] for coding style guidelines/discussion. | ||
We also need to cover: | |||
* how to namespace packages (e.g., <tt>require("foo/bar/baz")</tt>) | |||
* out-of-code documentation (e.g., tutorials and guides) | |||
* unit testing | |||
* memory leak detection | |||
* module unloading | |||
* security | |||
* localization | |||
Revision as of 00:20, 26 January 2010
The following are best practices for reboot development. Nothing is (yet) set in stone, so propose and debate and stuff.
- See Labs/Jetpack/Reboot/Style_Guide for coding style guidelines/discussion.
We also need to cover:
- how to namespace packages (e.g., require("foo/bar/baz"))
- out-of-code documentation (e.g., tutorials and guides)
- unit testing
- memory leak detection
- module unloading
- security
- localization