canmove, Confirmed users
1,567
edits
Firefox/Projects/Extension Manager API: Difference between revisions
Firefox/Projects/Extension Manager API (view source)
Revision as of 12:03, 30 June 2009
, 30 June 2009→Goals / Use Cases
| Line 7: | Line 7: | ||
= Goals / Use Cases = | = Goals / Use Cases = | ||
* Support a wider range of add-on types managed through the same | * Support a wider range of add-on types managed through the same API | ||
* Allow application/extension developers to be able to easily query the state of installed items | * 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 | * Make it easier for applications to replace the add-ons UI with their own implementation by making all necessary information available through the defined API | ||
* Remove direct access to the datastore | |||
* Simplify the internal code and speed up startup times | * Simplify the internal code and speed up startup times | ||
* Minimize the use of RDF throughout the backend | * Minimize the use of RDF throughout the backend to allow for easy replacement in the future | ||
* Remove | * Migrate from an RDF based datastore to an SQLite based datastore | ||
* Remove extensions.cache | |||
* Reduce the number of unnecessary restarts during startup | |||
= Design = | = Design = | ||