Labs/Jetpack/JEP/28: Difference between revisions

Jump to navigation Jump to search
→‎Motivation and Rationale: removed some repetitive blathering
(→‎Abstract: added xulrunner apps as a target)
(→‎Motivation and Rationale: removed some repetitive blathering)
Line 5: Line 5:
== Motivation and Rationale ==
== Motivation and Rationale ==


In many ways, this JEP is a refactored formalization of Jetpack's current implementation that will allow many of Jetpack's core benefits to be leveraged by any XULRunner Extension. Another way of putting this is that Cuddlefish nicely decouples functionality that is specific to Jetpack from functionality that many other extensions—Labs extensions in particular—would like to have, and which they often end up re-implementing from scratch to some extent.
In many ways, this JEP is a refactored formalization of Jetpack's current implementation that will allow many of Jetpack's core benefits to be leveraged by any XULRunner Extension.


Additionally, by moving to a SecurableModule-based architecture, Jetpack's runtime can easily be decoupled from the about:jetpack page, which will resolve a number of deficiencies (such as the inability to look at the API documentation and use the built-in code editor simultaneously).
Additionally, by moving to a SecurableModule-based architecture, Jetpack's runtime can easily be decoupled from the about:jetpack page, which will resolve a number of deficiencies (such as the inability to look at the API documentation and use the built-in code editor simultaneously).
874

edits

Navigation menu