1
edit
m (Reverted edit of Adolphus Bluxo, changed back to last version by TastyWheat) |
|||
(27 intermediate revisions by 16 users not shown) | |||
Line 1: | Line 1: | ||
{{FeatureBrainstorming}} | {{FeatureBrainstorming}} | ||
''What's the difference between 'Add-on management' and 'Add-on manager'?'' | |||
== Add-on access == | |||
We need direct access to addon/plugin-website so add a direct link on the Tools/Addons list. | |||
*This will allow us to bypass mozilla and comment and access directly to the addon/plugin. | |||
== Add-on management == | == Add-on management == | ||
Line 13: | Line 19: | ||
** 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) | ***Options are good, but this is unnecessary. Keep this as an add-on. --[[User:Armaetin|Armaetin]] 17:46, 24 January 2007 (PST) | ||
****STOP using "Groupthink". It doe's not help the process, it hinders it significantly. The OP has it exactly right. Maybe not ALL of these features should be added by default, but the majority of them are already on other ares in the application. It just seems ridiculous and lazy to not add them. If you don't like the idea, then add an "on/off" option to it. That solves it for everyone. Thinking that the rest of the world feels like you do or that you are supiour to everyone else, is absurd. It should have as many functions as it possibly can. This is what makes a good multi/research app. We at least need sort functions, BADLY, for the extension list window. | |||
* 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 I agree. --[[User:Armaetin|Armaetin]] 17:46, 24 January 2007 (PST) | **If there are no consequences to be concerned over, then I agree. --[[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. | ||
* How about a Foxmarks-style feature that encompasses not just bookmarks, but extensions, themes, search-engines, and settings? New users could configure it on first-load, and old-users, when using different computers, could login and have their favorite stuff instantly downloaded and installed instead of spending ten minutes searching for everything. More details and mockups of the idea here: [http://www.hell-toupee.com/foxperience] | |||
* When an extension is downloaded from an untrusted site, the user should be given a dialogue telling them that, giving details of the site (to prevent phishing), asking them if they really want to install it, and giving them an option to do so. At the moment, it just gets blocked, and the only way round it is to add that site to your list of trusted sites. This is not only really clunky, it's a security hole - just because i trust the site for this extension doesn't mean i want to trust it ever again. If it's thought that this is not a good default behaviour, it should at least be allowed as an 'expert/reckless lunatic mode'. | |||
* Make add-ons visible for the current or all profiles at the user's choice, if easily possible. This avoids having "standard" extensions (e.g. RIP) to be installed over and over again. See item in the "Add-on manager" section about single/all users also. --ThomasP | |||
== Add-on manager == | == Add-on manager == | ||
Line 44: | Line 54: | ||
* For the "Themes" tab of the Add-on manager, always keep the "Firefox (default)" theme on top, maybe with a separator under it, and then alphabetize the user-added themes below that. | * For the "Themes" tab of the Add-on manager, always keep the "Firefox (default)" theme on top, maybe with a separator under it, and then alphabetize the user-added themes below that. | ||
*When switching themes, put a "Restart Firefox" button just like when you install an extension. I don't like to have the "save tabs on shutdown" option enabled, so a restart button saves me from remembering all of my tabs. There is one for after installing add-ons, so I don't see why there isn't one for switching themes, since it requires a restart. | *When switching themes, put a "Restart Firefox" button just like when you install an extension. I don't like to have the "save tabs on shutdown" option enabled, so a restart button saves me from remembering all of my tabs. There is one for after installing add-ons, so I don't see why there isn't one for switching themes, since it requires a restart. | ||
*Fully automatic Add-on Update a-la Windows - optional: | |||
**DO NOT prompt before downloading and installing updates for add-ons - just do it. It disturbs the flow too much. When was the time someone actually chose not to update? | |||
**DO NOT ask to restart - just wait till next start. | |||
**DO NOT show updated add-ons window after restart - just show a little notifier icon somehere out of the way with a tooltip showing the list of updated add-ons if you move your mouse over it. | |||
**DO silently succeed! | |||
*** Seconded! [[User:Nonzenze|Nonzenze]] 18:15, 18 December 2008 (UTC) | |||
== Remote extensions == | == Remote extensions == | ||
Line 58: | Line 74: | ||
**Disabling extensions is now possible in Firefox 2.0.0.1. However, enabling and disabling an extension requires the restarting of Firefox. The dynamic installing/uninstalling of add-ons could allow an external program to force feed a bug into Firefox, but I don't see how that's possible with dynamic disable/enabling of extentions. --[[User:Armaetin|Armaetin]] 15:16, 31 December 2006 (PST) | **Disabling extensions is now possible in Firefox 2.0.0.1. However, enabling and disabling an extension requires the restarting of Firefox. The dynamic installing/uninstalling of add-ons could allow an external program to force feed a bug into Firefox, but I don't see how that's possible with dynamic disable/enabling of extentions. --[[User:Armaetin|Armaetin]] 15:16, 31 December 2006 (PST) | ||
*When disabling or uninstalling an add-on, put a "Restart Firefox" button just like when you add an add-on. I don't like to have the "save tabs on shutdown" option enabled, so a restart button saves me from remembering all of my tabs. There is one for after installing add-ons, so I don't see why there isn't one for disabling or uninstalling add-ons. | *When disabling or uninstalling an add-on, put a "Restart Firefox" button just like when you add an add-on. I don't like to have the "save tabs on shutdown" option enabled, so a restart button saves me from remembering all of my tabs. There is one for after installing add-ons, so I don't see why there isn't one for disabling or uninstalling add-ons. | ||
*Add an option to protect the enabling/disabling of a plugin with a password. This is essential to use firefox in a work/buisiness environment and it's also quite a nice feature for some specific plugins. For example; it is now easy to disable the adult filter plugins. For these kinds of add-ons, password protection is essential. | |||
== Syncable Add-ons data/prefs == | == Syncable Add-ons data/prefs == | ||
Line 67: | Line 85: | ||
* Have "Extension Packs" available for download immediately upon completing a Firefox install (also see "Installer" and "Uncategorized: Firefox Core/More" notes) | * Have "Extension Packs" available for download immediately upon completing a Firefox install (also see "Installer" and "Uncategorized: Firefox Core/More" notes) | ||
* '''Firefox Core/More''' solution (under [[Firefox/Feature Brainstorming:Other or Uncategorized|Other or Uncategorized]]) will handle both extensions packs on install, intuitive configuration and trust. | * '''Firefox Core/More''' solution (under [[Firefox/Feature Brainstorming:Other or Uncategorized|Other or Uncategorized]]) will handle both extensions packs on install, intuitive configuration and trust. | ||
* Export/Save Extensions (as backup) used/installed. | |||
== Restrictions == | == Restrictions == | ||
Line 93: | Line 112: | ||
* Button "Don't show again" for Plugin bar... Sometimes I just don't want a plugin like Flash and don't want to be reminded on that on every page with advertizing. | * Button "Don't show again" for Plugin bar... Sometimes I just don't want a plugin like Flash and don't want to be reminded on that on every page with advertizing. | ||
* Support for executing a .NET Framework code. | * Support for executing a .NET Framework code. | ||
* Bulk application reassignment (I want to be able to change everything from QuickTime plugin to something that works like VLC or MPC) | |||
== Plug-in for non integrated formats == | == Plug-in for non integrated formats == | ||
Line 139: | Line 159: | ||
==View new extensions== | ==View new extensions== | ||
*Instead of (or as well as) this view: https://addons.mozilla.org/search.php?app=firefox&appfilter=firefox&type=E&sort=newest there should be an option to view all the *new* extensions, most recent first (if this isn't the place to make such comments, lease move it there. Thank you.) [[User:Pigsonthewing|Pigsonthewing]] 08:14, 11 December 2006 (PST) | *Instead of (or as well as) this view: https://addons.mozilla.org/search.php?app=firefox&appfilter=firefox&type=E&sort=newest there should be an option to view all the *new* extensions, most recent first (if this isn't the place to make such comments, lease move it there. Thank you.) [[User:Pigsonthewing|Pigsonthewing]] 08:14, 11 December 2006 (PST) | ||
*Une extension so that Thunderbird is open when Firefox is open | |||
== References == | == References == | ||
Line 155: | Line 176: | ||
== Rollback Extensions == | == Rollback Extensions == | ||
* Keep the last n versions of an extension around and allow rollback if the user doesn't like the newest version. | * Keep the last n versions of an extension around and allow rollback if the user doesn't like the newest version. | ||
== Combine Themes == | |||
* The ability to combine themes, similar to the behavior in [http://img88.imageshack.us/img88/8040/kg17li7.gif Ubuntu GNOME's theme editor]. It could allow the user to say "Use icons from theme x, use tabs from theme y, use window color from theme z". I would like this because there are some great themes out there, but most of them do not change the look of Firefox 2.0's tabs, which I do not like the look of. I would like to be able to use, say, [https://addons.mozilla.org/firefox/7/ Qute] icons with [https://addons.mozilla.org/firefox/3479/ Winestripe] tabs. --[[User:JohnnyK|JohnnyK]] 09:46, 4 March 2007 (PST) | |||
== Parallel Themes == | |||
During my work, i usually can open a browser window dedicated to one topic and another one dedicated to another topic. each of these windows has a set of tabs inside it. it would be a good idea to apply a theme to the first window while keeping the other window with a different theme, effectively having "parallel" themes (like parallel processing). This will create a visual aid to help me know which mind thread a window (and all its tabs) belong to. | |||
This of course could be pushed further if Microsoft allows me to define my own taskbar groups, so that i can have more than one group of FireFox in the taskbar, one for each mind thread. | |||
--[[User:Mb2nd|Mb2nd]] 31 March 2007 | |||
== Custom bookmark with partially blank values == | |||
* I often feel the need to be able to insert, or replace values in an URL. Therefore it would be nice with a custom bookmark where I could set some of the URL as blank, and write that blank spot when I were to open the bookmark. An example could be: | |||
** A YouTube user profile URL looks like: www.youtube.com/profile?user=kebakent | |||
* I would like to write a username, and then visit that profile without worrying about the rest of the URL. So I could make a bookmark called www.youtube.com/profile?user=USERNAME and then be prompted for the username every time I opened the bookmark. Thereby I could visit any profile I would like. This would be practical in so many ways. --[[User:Keba|Keba]] 19:22, 8 December 2007 (PST) | |||
== JavaScript cache == | |||
Pages like gmail and similar web 2.0 (and maybe future web 3.0) apps downloads huge amount of data everytime it loads. However if the javascript they use is simply stored in the user's computer like an addon, it is obviously going to be much faster. For example, the collection of all the gamil's javascripts and other files can be packed into a zipped file and be available for download. Any update by google can be available as a small change to the package instead of downloading the entire stuff again. Also, if some library like domTT is used in many websites, it wont be required to load the full library everytime as we already would have it installed in our firefox. |
edit