Confirmed users
1,100
edits
Jetpack/Roadmap/2013: Difference between revisions
→SDK API Development
Canuckistani (talk | contribs) |
Canuckistani (talk | contribs) |
||
| Line 61: | Line 61: | ||
When we provide a new high-level api in the SDK, that api must provide a clear benefit to the add-on develop in terms of ease of use while still not impacting Firefox performance. | When we provide a new high-level api in the SDK, that api must provide a clear benefit to the add-on develop in terms of ease of use while still not impacting Firefox performance. | ||
# Places API. Bookmarks and history are probably the most interesting stores of data in Firefox and in particular the most interesting to users. Providing performant and usable apis to access this data easily could enable all manner of browser / user innovations. | # Places API. [DONE] [https://bugzilla.mozilla.org/show_bug.cgi?id=545700 Tracking Bug] Bookmarks and history are probably the most interesting stores of data in Firefox and in particular the most interesting to users. Providing performant and usable apis to access this data easily could enable all manner of browser / user innovations. | ||
# Awesomebar API. The awesomebar is *the* primary piece of browser UI, used more than anything else. As experiments like Bryan Clarke's [https://github.com/clarkbw/searchspot/tree/awesomebar searchspot add-on] have shown us, it can be very powerful to inject custom results into the awesomebar. | # Awesomebar API. The awesomebar is *the* primary piece of browser UI, used more than anything else. As experiments like Bryan Clarke's [https://github.com/clarkbw/searchspot/tree/awesomebar searchspot add-on] have shown us, it can be very powerful to inject custom results into the awesomebar. | ||