99
edits
Firefox/Feature Brainstorming:Add-ons: Difference between revisions
Jump to navigation
Jump to search
Firefox/Feature Brainstorming:Add-ons (view source)
Revision as of 01:46, 25 January 2007
, 25 January 2007→Add-on management
| Line 8: | Line 8: | ||
* Extensions should have compatibility mode to allow older extensions to run when a new revision of firefox is released and extension is not available. Maybe offer a "force install" to see if an out of revision extension will work. | * Extensions should have compatibility mode to allow older extensions to run when a new revision of firefox is released and extension is not available. Maybe offer a "force install" to see if an out of revision extension will work. | ||
** See ''Nightly Tester Tools'' extension that is able to force such install mode over any given extension (or at least over most of them). | ** See ''Nightly Tester Tools'' extension that is able to force such install mode over any given extension (or at least over most of them). | ||
***If this doesn't cause any problems in Firefox, then yes, backwards compatibility with old extensions is needed, --[[User:Armaetin|Armaetin]] 17:46, 24 January 2007 (PST) | |||
*Should be able to view date and time that extension was added, and sort extensions by that date (to aid debugging, by removing extensions in reverse order, until a recently-seen problem ceases to exist). Andy Mabbett | *Should be able to view date and time that extension was added, and sort extensions by that date (to aid debugging, by removing extensions in reverse order, until a recently-seen problem ceases to exist). Andy Mabbett | ||
* Offer a program that allows users to merely alter the color scheme of the Firefox. All gloss effects and UI aesthetics remain, save for the change in color. Once the desired hue is selected, it's as easy as naming, then applying that theme. The program takes care of the rest. | * Offer a program that allows users to merely alter the color scheme of the Firefox. All gloss effects and UI aesthetics remain, save for the change in color. Once the desired hue is selected, it's as easy as naming, then applying that theme. The program takes care of the rest. | ||
** This sort of option should be kept as an extension for FF, as when you add too many sorts of options like this, you end up with a browser that has too much in it (akin to [eek!] IE). --[[User:FlyingIsFun1217|FlyingIsFun1217]] 14:06, 1 January 2007 (PST) | ** This sort of option should be kept as an extension for FF, as when you add too many sorts of options like this, you end up with a browser that has too much in it (akin to [eek!] IE). --[[User:FlyingIsFun1217|FlyingIsFun1217]] 14:06, 1 January 2007 (PST) | ||
***Options are good, but this is unnecessary. Keep this as an add-on. --[[User:Armaetin|Armaetin]] 17:46, 24 January 2007 (PST) | |||
* If it's possible, changing the theme without restarting (like it's managed in Songbird) would be great. | * If it's possible, changing the theme without restarting (like it's managed in Songbird) would be great. | ||
** As long as FF does not become adversely affected by this (things such as graphical artifacts that may be common when switching themes), I fully support this idea. Restarting can take long on a laptop with a slow hard drive :( --[[User:FlyingIsFun1217|FlyingIsFun1217]] 14:06, 1 January 2007 (PST) | ** As long as FF does not become adversely affected by this (things such as graphical artifacts that may be common when switching themes), I fully support this idea. Restarting can take long on a laptop with a slow hard drive :( --[[User:FlyingIsFun1217|FlyingIsFun1217]] 14:06, 1 January 2007 (PST) | ||
**If there are no consequences to be concerned over, then agreed. --[[User:Armaetin|Armaetin]] 17:46, 24 January 2007 (PST) | |||
* Since most extensions are of a small size, could extensions be mirrored on our hard drives in .xpi format? This way, one can open up the Profile folder, drag-and-drop all extensions into the Addon Manager and reinstall all extensions in case of a crash. This not only saves the user time and addons.mozilla.org bandwidth, it also reduces stress and frustration due to the loss of a profile and speeds up the restoring process. (thus preventing temptation from Opera and IE) If huge extensions start popping up, which I doubt, an about:config setting could be added to only mirror extensions that are less than a specific amount of KB. A plain text file/ xml file could be placed in the mirror directory with the names of excluded extensions. | * Since most extensions are of a small size, could extensions be mirrored on our hard drives in .xpi format? This way, one can open up the Profile folder, drag-and-drop all extensions into the Addon Manager and reinstall all extensions in case of a crash. This not only saves the user time and addons.mozilla.org bandwidth, it also reduces stress and frustration due to the loss of a profile and speeds up the restoring process. (thus preventing temptation from Opera and IE) If huge extensions start popping up, which I doubt, an about:config setting could be added to only mirror extensions that are less than a specific amount of KB. A plain text file/ xml file could be placed in the mirror directory with the names of excluded extensions. | ||