874
edits
Labs/Jetpack/Reboot FAQ: Difference between revisions
added another question
(added more to answer) |
(added another question) |
||
| Line 82: | Line 82: | ||
Our ultimate goal is to make the reboot as easy to develop extensions with and iterate on as the prototype. Right now, the reboot is essentially the underlying command-line tools that a front-end IDE will use to make things much easier to use. This front-end IDE will have similar developer ergonomics to the original prototype's interface. When everything is finished, Jetpack developers will download and install a "Jetpack SDK" that will automatically set up a cfx/jpx environment and the front-end IDE on the developer's computer. | Our ultimate goal is to make the reboot as easy to develop extensions with and iterate on as the prototype. Right now, the reboot is essentially the underlying command-line tools that a front-end IDE will use to make things much easier to use. This front-end IDE will have similar developer ergonomics to the original prototype's interface. When everything is finished, Jetpack developers will download and install a "Jetpack SDK" that will automatically set up a cfx/jpx environment and the front-end IDE on the developer's computer. | ||
'''Why can't I install, uninstall and upgrade Jetpacks without restarting the browser anymore?''' | |||
Because Jetpacks are currently being built as bootstrapped XPIs that have no dependencies, we're actually building-in the notion of "extensions that know how to unload themselves" into the Mozilla platform itself. Until we build this into the platform, however, we won't be able to manage Jetpacks without rebooting--even though "under the hood" the Jetpack platform knows how to unload its resources without rebooting. For more information on this, see [http://www.toolness.com/wp/?p=746#comment-2631 comments on Atul's blog post]. | |||