Confirmed users
587
edits
Firefox/Projects/Jetpack Uplift Exploration/Notes: Difference between revisions
Firefox/Projects/Jetpack Uplift Exploration/Notes (view source)
Revision as of 23:23, 20 July 2009
, 20 July 2009→Questions
| Line 107: | Line 107: | ||
== Questions == | == Questions == | ||
=== General === | |||
* Would uplift include renaming? | |||
** Jetpack is a good code name, but maybe not a good feature name | |||
** At least, may make sense to rename "jetpack" object to "env" or similar | |||
=== For the Jetpack team === | === For the Jetpack team === | ||
| Line 116: | Line 122: | ||
* Would it make sense to put all APIs in IDLs? | * Would it make sense to put all APIs in IDLs? | ||
** Potentially slower, but more secure. | ** Potentially slower, but more secure. | ||
* | * How stable are Jetpack's APIs right now? Does it make any sense to include some of them in Firefox itself for Jetpack to use so we can handle changes as Firefox is upgraded rather than Jetpack having to cope? | ||
* Is Jetpack having to use any ugly or private means to get at the functionality it requires in the platform that it might make sense for us to expose in some stable API? | * Is Jetpack having to use any ugly or private means to get at the functionality it requires in the platform that it might make sense for us to expose in some stable API? | ||
* Is there any part of the security model that it would be helpful to uplift into Firefox and perhaps make available for add-on developers using the full XPI route to use if they want to keep things safer? | * Is there any part of the security model that it would be helpful to uplift into Firefox and perhaps make available for add-on developers using the full XPI route to use if they want to keep things safer? | ||