Labs/Extensions2: Difference between revisions

(New page: = Extensions 2.0: Ent = == State of the Art == Add-Ons are the lifeblood of Firefox -- enabling anyone to make the browser theirs. We have thousands of add-ons, and add-on creators. It'...)
 
Line 11: Line 11:
Enhancing the browser should be as easy as it is to write a web page. The time between having an idea, and an implementation should be as short as possible: Programming a working add-on for each of the major add-on types should take less than 5 minutes from start to running in the browser.
Enhancing the browser should be as easy as it is to write a web page. The time between having an idea, and an implementation should be as short as possible: Programming a working add-on for each of the major add-on types should take less than 5 minutes from start to running in the browser.


(1) 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.
# '''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.
# '''Develop Once, Run Anywhere, Any Version'''.
(2) 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.
 
##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.
  - 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.
#'''Secure'''
 
  - 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.
 
(3) 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 41: Line 37:


*It may seem odd that this is referred to as a manifesto, as it is not hundreds of pages long and has not been written by someone with an unkempt beard and filthy military surplus clothing. We believe in simplicity in all its forms. That is why we are inclined toward brevity. And why we shower.
*It may seem odd that this is referred to as a manifesto, as it is not hundreds of pages long and has not been written by someone with an unkempt beard and filthy military surplus clothing. We believe in simplicity in all its forms. That is why we are inclined toward brevity. And why we shower.


== Road Map ==
== Road Map ==
577

edits