Summit2008/Sessions/Proposals/Add-on Manager/Session Notes: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
 
No edit summary
Line 8: Line 8:
** How do we handle updates to add-ons which don't have a locale pack available. (See add-on dependency stuff).
** How do we handle updates to add-ons which don't have a locale pack available. (See add-on dependency stuff).
** Possibly offer fallbacks - not good for chrome systems (DTD can't do it but property files can).
** Possibly offer fallbacks - not good for chrome systems (DTD can't do it but property files can).
* Dependency resolution
* Dependency resolution
** First request - show the dependency
** First request - show the dependency
Line 14: Line 13:
** AMO should reflect add-on dependencies
** AMO should reflect add-on dependencies
** AMO sees the dependency at the system level and dynamic generation of AMO (AMO may need to see what is already installed). Client might ignore it.
** AMO sees the dependency at the system level and dynamic generation of AMO (AMO may need to see what is already installed). Client might ignore it.
* Conflict Resolution
** Everyone will start blocking a list of a series of extensions
** Without it, it incentivizes add-ons authors to disable other authors
* Install without Restart
** Perhaps close and restart a window?
** Remember that you need to support more than the Firefox app (these apps don't have session restore as a saving grace)
** Encourage folks to use dynamic overlays
** Perhaps allow sandboxing of add-ons based on what they do. Create widgets or limited capability add-ons.
** Flipping a flag that allows add-on authors to claim "Needs a restart" might have detrimental effects
** Allow profile version management (to allow testing of add-ons) similar to Vista/XP's snapshot/restore (and Firefox's bookmarks restore), etc...


*
*
1,071

edits

Navigation menu