- I'm really sorry, if I've overlooked something, but is there a clear-cut place to find out what "Jetpacks" (Jetpack-based Addons) can do NOW?...& what they can't do YET, but is planned? Yes, I could probably scour Bugzilla for hours & find technical jargon...& I've seen the stuff about "JEPs" in a Wiki somewhere, but is there any place that lists, in plain English, what can be done NOW (& what CAN'T be done) in Jetpack-based Addons? I'm not even sure what "Normal" Addons can do, let alone what "Jetpacks" can do.
For a real-world example, I wanna update/rewrite NoUn Buttons (& give it a better name: "Unmerge Back & Forward Buttons (& Menus)"), it has not been updated for Firefox 4 & the author has stated, in a non-English forum, that he don't plan on updating it (for various reasons) (however, I have not E-mailed him about this yet). So, minimally, I wanna update it so it works on Firefox 4. It's a "non-Jetpack" Addon, so 1st I'll probably just "get it working" on Firefox 4, but in the long-run I'd like to convert it to a Jetpack, so it can be installed without a restart, but I don't know if Jetpacks can "Unmerge" Toolbar buttons...or even add new buttons?
That sounds like simple functionality (modifying a Toolbar/adding/changing buttons), but can Jetpacks do that yet? Where should I look to find out? Wouldn't this Forum, in a Sticky, be a good place for this plain-English run-down of "What Jetpack can do NOW?".
Looking at the source of the Jetpack SDK 1.0b5, under addon-sdk-1.0b5\packages\addon-kit\lib, there are these filenames...
- I would also like to take this time to recommend a different approach to installing the Jetpack SDK (for use in Addons, not in Development). Currently, every Jetpack-based Addon includes/installs the entire SDK. I think it would be better, if each Jetpack-based Addon would only include a reference to what SDK version the Addon requires (which version it was created/tested with), then Firefox would install that SDK version for that Addon. If the user installs another Addon, requiring the same Jetpack SDK version, nothing would happen, Firefox would NOT install another copy of the same SDK version...all Addons (using the same version) would just share the 1 copy (of that version). Furthermore, when an Addon is updated & is now based on a new Jetpack SDK version, that new version of the SDK would be installed & the old version of the SDK would be uninstalled (if it's no longer in-use by any other Addons). I think I read somewhere that they might've wanted to do this, but I'm not sure if this is exactly what they meant. This way, only 1 copy of each version of the Jetpack SDK is installed...& all Addons can share that 1 copy.