1,457
edits
Samuelsidler (talk | contribs) |
|||
| Line 13: | Line 13: | ||
# '''Use Web Technology''' | # '''Use Web Technology''' | ||
#*HTML, Javascript, and CSS should be the only tools required to create an add-on. No XUL or XBL required. If you are already a web developer, you know all you need to write an add-n. | #*HTML, Javascript, and CSS should be the only tools required to create an add-on. No XUL or XBL required. If you are already a web developer, you know all you need to write an add-n. | ||
# '''Develop Once, Run Anywhere, Any Version'''. | # '''Develop Once, Run Anywhere, Any Version'''. | ||
#* Writing an add-on for Firefox should run in Firefox Mobile, Thunderbird, and anywhere else that's apropos. Programming should be by intent: You should be able to say, "My add-on should expose UI in a toolbar-like thing", and it will. Whatever a toolbar-like thing happens to be on Fennec, Firefox, etc. | #* Writing an add-on for Firefox should run in Firefox Mobile, Thunderbird, and anywhere else that's apropos. Programming should be by intent: You should be able to say, "My add-on should expose UI in a toolbar-like thing", and it will. Whatever a toolbar-like thing happens to be on Fennec, Firefox, etc. | ||
#* As a developer, you shouldn't have to worry about some detail-of-Firefox internals changing breaking your extension. Add-ons will work through a version'ed facade-pattern so that you won't be in a constant struggle to keep your extension working with the latest FF edition. | #* As a developer, you shouldn't have to worry about some detail-of-Firefox internals changing breaking your extension. Add-ons will work through a version'ed facade-pattern so that you won't be in a constant struggle to keep your extension working with the latest FF edition. | ||
#'''Secure''' | #'''Secure''' | ||
#* Add-ons should have access to only the privileges they need. They should be as safe and secure as Firefox proper. | #* Add-ons should have access to only the privileges they need. They should be as safe and secure as Firefox proper. | ||
| Line 24: | Line 22: | ||
#* Security should always be presented in human-terms, not technical-terms. | #* Security should always be presented in human-terms, not technical-terms. | ||
#* More secure add-ons should enjoy a more streamlined user experience for installation. | #* More secure add-ons should enjoy a more streamlined user experience for installation. | ||
# '''Easy to code''' | # '''Easy to code''' | ||
#* The API should be small, short, concise. | #* The API should be small, short, concise. | ||
| Line 31: | Line 28: | ||
#* Changes made during development should be reflected in real-time in the browser | #* Changes made during development should be reflected in real-time in the browser | ||
#* Great documentation. Tutorials, snippets, examples. | #* Great documentation. Tutorials, snippets, examples. | ||
# '''Easy to install, easy to use, easy to keep up-to-dates''' | # '''Easy to install, easy to use, easy to keep up-to-dates''' | ||
#* Add-ons should feel light-weight: they should be installable without restart and in two clicks or less | #* Add-ons should feel light-weight: they should be installable without restart and in two clicks or less | ||
edits