Labs/Jetpack/Reboot/FAQ: Difference between revisions

Jump to navigation Jump to search
"Our ultimate goal is to the make the reboot s/as easy/easier/..."
(Copied from https://wiki.mozilla.org/Labs/Jetpack/Reboot_FAQ)
 
("Our ultimate goal is to the make the reboot s/as easy/easier/...")
 
Line 7: Line 7:
'''Why is the Jetpack reboot so much harder to use than the original Jetpack prototype?'''
'''Why is the Jetpack reboot so much harder to use than the original Jetpack prototype?'''


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 ''easier'' to develop extensions with and iterate on than 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?'''
'''Why can't I install, uninstall and upgrade Jetpacks without restarting the browser anymore?'''
Confirmed users
764

edits

Navigation menu