577
edits
Line 13: | Line 13: | ||
# '''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'''. | # '''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. | |||
#'''Secure''' | #'''Secure''' | ||
edits