13
edits
Firefox:Extension Manager UI: Difference between revisions
Firefox:Extension Manager UI (view source)
Revision as of 19:13, 13 November 2010
, 13 November 2010no edit summary
No edit summary |
|||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 56: | Line 56: | ||
Extensions are categorized on the web site, so why can't that categorization follow into the UI? Especially if a lot of extensions are loaded, and especially if I forgot which did what, a categorized list would be oh-so-helpful! | Extensions are categorized on the web site, so why can't that categorization follow into the UI? Especially if a lot of extensions are loaded, and especially if I forgot which did what, a categorized list would be oh-so-helpful! | ||
=== | === Reply by [[User:Dasch|Daniel Schierbeck]] === | ||
The problem with your suggestion is that many, if not most extensions have multiple categories. Should the extensions then also appear under more than one category, like they do on the Mozilla Update site? That would only serve to make the extension list longer and more complex. | The problem with your suggestion is that many, if not most extensions have multiple categories. Should the extensions then also appear under more than one category, like they do on the Mozilla Update site? That would only serve to make the extension list longer and more complex. | ||
| Line 72: | Line 72: | ||
Following on from what Robert said about updates, I think that the default action of the 'Check for Updates' option on the Help menu should be to check for updates for everything - Core, Extensions and Themes. There should also be some notification for extension and theme updates in the same way that there is for new versions of the browser. I know more than a few people who have extensions installed and who don't ever open the EM or TM to check for updates, so they are stuck with the old version of the extension until the old version breaks when the browser updates itself! | Following on from what Robert said about updates, I think that the default action of the 'Check for Updates' option on the Help menu should be to check for updates for everything - Core, Extensions and Themes. There should also be some notification for extension and theme updates in the same way that there is for new versions of the browser. I know more than a few people who have extensions installed and who don't ever open the EM or TM to check for updates, so they are stuck with the old version of the extension until the old version breaks when the browser updates itself! | ||
== Comment by [[User: | == Comment by [[User:Amal]] == | ||
Perhaps this would take some development time and excessive server load, but I think it would be cool to create an initial browser configuration on the web site. Before you initially download firefox, you would take a brief survey regarding your preferences for configuration. The site will then compile an installer package for you with the appropriate settings and extensions included. If you don't like it, you can change things around the old ways or perhaps retake the survey and have your firefox "updated". | Perhaps this would take some development time and excessive server load, but I think it would be cool to create an initial browser configuration on the web site. Before you initially download firefox, you would take a brief survey regarding your preferences for configuration. The site will then compile an installer package for you with the appropriate settings and extensions included. If you don't like it, you can change things around the old ways or perhaps retake the survey and have your firefox "updated". | ||
| Line 115: | Line 115: | ||
| [ Update all extensions ] [ Close ] | | | [ Update all extensions ] [ Close ] | | ||
'------------------------------------------------------------' | '------------------------------------------------------------' | ||
</pre> | |||
==Comment by [[User:Foxxen2|Foxxen2]]== | |||
* I do think that the general update function should watch extension and theme updates too, because the less a user has to do of maintenance, the better in general. Especially: | |||
** If a core update would break an extension or theme, by default shouldn't allow incompatible modules to run without a user override, and it should draw attention to the potential risks of override: "Only do this if you are sure, the author has not guaranteeed compatibility." | |||
** Provide for advanced users, a list of updates found, with check boxes next to each. ("Autopatcher" [[:Image:Autopatcher screenshot.png|screenshot]] does this very neatly) | |||
* I'd be happy to see options for individual extensions open up a general options box that controlled all options for all modules in FF. Only thing is, not to make it too confusing. One common option box would be a sensible idea -- extensions manager takes the user directly to the option box for that extension. Maybe under the "tools" menu there's "General Options..." and "Extension and theme options..."? | |||
* Some other aspects of extension manager I commented on one of the forums, not sure whether to repost here or just link, but they are significant ones. Some relate to user security. [http://forums.mozillazine.org/viewtopic.php?t=399361 link] | |||
==Comment by Muescha== | |||
it would be nice, if the extension manager let me install XPI-Files not only for FireFox but also Thunderbird (and other applications). so i can click and install a thunderbird extension with one-click (and not with rightclick, downloading, search the local file, run FB extensionmanager etc). | |||
maybe after opening a XPI-File: | |||
<pre> | |||
|----------------------------------------------------| | |||
| Extension Manager Install | | |||
|----------------------------------------------------| | |||
| | | |||
| Extension Name: ForecastFox | | |||
| | | |||
|----------------------------------------------------| | |||
| | | |||
| install for: [X] FireFox 1.5.0.3 | | |||
| [ ] Thunderbird 1.5 | | |||
| --- Seamonkey (not installed) | | |||
| --- Songbird (not supported) | | |||
| | | |||
|----------------------------------------------------| | |||
</pre> | </pre> | ||