canmove, Confirmed users
548
edits
Jetpack/Roadmap: Difference between revisions
Jump to navigation
Jump to search
→Top Priorities
| Line 107: | Line 107: | ||
from the add-on bar to the top of Firefox. | from the add-on bar to the top of Firefox. | ||
1) Mobile | |||
We must continue our work on making the development of add-ons for | We must continue our work on making the development of add-ons for Firefox mobile easy and familiar using the same APIs and tools used to create desktop add-ons. We still have a good deal of scope to figure out with mobile add-ons as there have been so few created to this point, and a small amount of usage. To that end, we are unsure which use-cases are the most desired for mobile add-ons. | ||
Firefox mobile easy and familiar using the same APIs and tools used to | |||
create desktop add-ons. We still have a good deal of scope to figure | |||
out with mobile add-ons as there have been so few created to this | |||
point, and a small amount of usage. To that end, we are unsure which | |||
use-cases are the most desired for mobile add-ons. | |||
Because of this lack of scope, we have decided to pick a couple of | Because of this lack of scope, we have decided to pick a couple of APIs which seem important to tackle early, get them running and see how people use them and what they ask for in addition to these. As we already have page-mods working, the two additional APIs we have decided to look at are: | ||
APIs which seem important to tackle early, get them running and see | |||
how people use them and what they ask for in addition to these. As we | |||
already have page-mods working, the two additional APIs we have | |||
decided to look at are: | |||
* [https://wiki.mozilla.org/Features/Jetpack/Jetpack-Mobile-Simple-Prefs Preferences API] | |||
This allows developers to add simple preferences to their add-on. We have just landed this for Desktop and need to make sure it works in Mobile. The initial scope suggests looking at the native android preferences screen as the UI, though that may change as we investigate. | |||
This is represented in the | |||
[https://wiki.mozilla.org/Features/Jetpack/Add-onTab-API feature page] | 2) Add-on Tab API | ||
for adding the add-on tab to Desktop Firefox, we simply need to port | |||
This is represented in the [https://wiki.mozilla.org/Features/Jetpack/Add-onTab-API feature page] for adding the add-on tab to Desktop Firefox, we simply need to port | |||
this over to mobile. | this over to mobile. | ||
===P1 APIs=== | ===P1 APIs=== | ||
1) [https://wiki.mozilla.org/Features/Jetpack/Jetpack-Chrome-mods Chrome-mods] | |||
Firefox has always presented itself to developers as a browser that allows customization. While this can often be painful from the point of view of user experience, it also provides great power in extensibility and innovation. Jetpack has always embraced the idea of modification and extension but only for shallow integrators where we felt some responsibility to help direct better user experience guidelines through offering only elements that would lend themseleves to that better experience. While that does a great deal to help keep the experience clean, it also frustrates those who want to integrate more deeply into the browser. With a new focus on Deep Integrators we want to take the modification idea to Firefox Chrome (user interface) in a similar manner in which we answered the modification question with web pages. | Firefox has always presented itself to developers as a browser that allows customization. While this can often be painful from the point of view of user experience, it also provides great power in extensibility and innovation. Jetpack has always embraced the idea of modification and extension but only for shallow integrators where we felt some responsibility to help direct better user experience guidelines through offering only elements that would lend themseleves to that better experience. While that does a great deal to help keep the experience clean, it also frustrates those who want to integrate more deeply into the browser. With a new focus on Deep Integrators we want to take the modification idea to Firefox Chrome (user interface) in a similar manner in which we answered the modification question with web pages. | ||
Chrome mods will allow the developer to easily alter Firefox chrome in a manner that is very similar to page-mods with the exception that the chrome being altered must first be properly identified before the developer can alter that element. | Chrome mods will allow the developer to easily alter Firefox chrome in a manner that is very similar to page-mods with the exception that the chrome being altered must first be properly identified before the developer can alter that element. | ||
2) Simpler Ctype API | |||
The initial scope of this is to add a utility that will help add-on developers who are working with binaries to be able to automatically scope their binary and include the proper headers, instantly, to their add-on. There may be greater scope once this is complete. In addition, we need to document how binaries can be used with the SDK. | |||
The | |||
3) Places API | |||
The crypto API will give SDK developers simple key/pair functionality | |||
to sign and verify data. | The Places API will allow developers access to the bookmarks menu, bookmarks tool, and possibly more. This needs more scope. | ||
4) [https://wiki.mozilla.org/AddonSDKCryptoAPI Crypto API] | |||
The crypto API will give SDK developers simple key/pair functionality to sign and verify data. | |||
5) [https://wiki.mozilla.org/Features/Jetpack/Jetpack-HTML-l10n Localization of HTML] | |||
We have developed a solution to localize strings within the code elements of jetpack add-ons, but many of them include text within HTML elements. We must ensure that we can also localize these HTML elements to have a more complete localization answer. In addition, the Mozilla platform supports the localization of XUL and XHTML via their DTDs and entity references, but there is no support for localizing HTML. We have the opportunity to change this and make localization better. | We have developed a solution to localize strings within the code elements of jetpack add-ons, but many of them include text within HTML elements. We must ensure that we can also localize these HTML elements to have a more complete localization answer. In addition, the Mozilla platform supports the localization of XUL and XHTML via their DTDs and entity references, but there is no support for localizing HTML. We have the opportunity to change this and make localization better. | ||
The next step for us in developing a better l10n experience is to add [https://wiki.mozilla.org/Features/Jetpack/Jetpack-HTML-l10n localizing static and dynamic text in HTML elements.] | The next step for us in developing a better l10n experience is to add [https://wiki.mozilla.org/Features/Jetpack/Jetpack-HTML-l10n localizing static and dynamic text in HTML elements.] | ||
6) [https://wiki.mozilla.org/Features/Jetpack/Jetpack-Move-Widgets-to-top Move Add-ons to top of browser] | |||
For a while we have talked about moving the widgets and panels the SDK | |||
provides to the top of the browser and away from the small add-on bar | For a while we have talked about moving the widgets and panels the SDK provides to the top of the browser and away from the small add-on bar at the bar. The UX team agrees with this move and has given us some guidance to go ahead and make this move. | ||
at the bar. The UX team agrees with this move and has given us some | |||
guidance to go ahead and make this move. | |||
= Secondary Priorities = | = Secondary Priorities = | ||