Firefox/Projects/Extension Manager API: Difference between revisions
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
* [22/06/09] - Implemented basic API framework and detection of items that need to be processed during startup. | * [22/06/09] - Implemented basic API framework and detection of items that need to be processed during startup. | ||
* [23/06/09] - Read manifest data from install.rdf and hook the public API up to the backend. Add tests that verify install location priorities and startup detection. | * [23/06/09] - Read manifest data from install.rdf and hook the public API up to the backend. Add tests that verify install location priorities and startup detection. | ||
* [24/06/09] - Performance improvements and hook app all manifest data in the database. Make public wrappers around internal data and add stubs for the install APIs. | |||
Revision as of 16:01, 24 June 2009
Overview
Sprint lead: Mossop
Reviewers: Rob Strong, sdwilsh
- Description
- When encountering a blocked or missing plugin, give the user a button to push that will download and run the plugin installer so they can see their content.
Goals / Use Cases
- Support a wider range of add-on types managed through the same interface
- Allow application/extension developers to be able to easily query the state of installed items
- Make it easier for applications to replace the add-ons UI with their own implementation
- Simplify the internal code and speed up startup times
Design
The new API is proposed at Extension Manager:API Rewrite
Bugs
Progress
- [22/06/09] - Implemented basic API framework and detection of items that need to be processed during startup.
- [23/06/09] - Read manifest data from install.rdf and hook the public API up to the backend. Add tests that verify install location priorities and startup detection.
- [24/06/09] - Performance improvements and hook app all manifest data in the database. Make public wrappers around internal data and add stubs for the install APIs.