|Firefox & add-ons UI mockups||Jeff Griffiths||3/13/12 2:12 PM|
In case you missed the weekly meeting today, Firefox UI designer Stephen
Horlander dropped by to show us these mockups:
I'll break down the capabilities based on our discussion with Stephen.
* there will be dedicated UI space for add-on buttons to the left of the
* add-on buttons are single-purpose, and can be 1 of 5 different types:
* Toggles: a button that is either on or off, and visually reflects this
* Panels: a button that displays an anchored panel, similar to how you
* Toolbars: a button that toggles the visibility of a toolbar
* Widgets: a 'live' widget of some sort that displays web content; the
* Sidebars: a button that toggles the visibility of a sidebar.
The last screenshots on that page illustrate how add-on buttons in the
We'd love any feedback regarding these concepts particularly from the
|Re: [jetpack] Firefox & add-ons UI mockups||Erik Vold||3/13/12 2:40 PM|
On 2012-03-13, at 2:12 PM, Jeff Griffiths <jgrif...@mozilla.com> wrote:
> * there will be dedicated UI space for add-on buttons to the left of the location bar, as well as the ability to place add-on buttons inside the location bar similar to how the Firefox Share add-on currently works.
The add-on bar is still an option right?
> * add-on buttons are single-purpose, and can be 1 of 5 different types: Toggles, Panels, Toolbars, Widgets and Sidebars
Maybe a menu type? submenus in a panel would be strange afaict.
Also imho FF shouldn't use one set of button types while add-on sdk users are forced to use a different type. Addon authors should be able to create buttons that match the style of native buttons.
> * Toolbars: a button that toggles the visibility of a toolbar
Users could still toggle the toolbar the normal way, without a button right?
> * Sidebars: a button that toggles the visibility of a sidebar.
Don't forget horizontal bars, they seem to be used too.
|Re: [jetpack] Firefox & add-ons UI mockups||Jeff Griffiths||3/13/12 3:01 PM|
On 12-03-13 2:40 PM, Erik Vold wrote:
My impression is that we want to kill the add-on bar.
>> * add-on buttons are single-purpose, and can be 1 of 5 different
I asked about this - the feeling was that an anchored panel should cover
> Also imho FF shouldn't use one set of button types while add-on sdk
I *think* the idea is that these would be the native buttons provided by
>> * Toolbars: a button that toggles the visibility of a toolbar
I don't know, but I assume so. I assume based on our history with this
>> * Sidebars: a button that toggles the visibility of a sidebar.
You mean, a Firebug/Web Console-style interface? This wasn't covered in
|Re: Firefox & add-ons UI mockups||Dave Townsend||3/13/12 10:53 PM|
There are a few more options than are shown in just those mockups. You can display your item as either a button in the location bar, a button in the toolbar or a small widget in the toolbar. Each of those can either be a toggle, a sidebar toggle, a toolbar toggle, open a panel, etc. though we may restrict the larger widgets from some of those behaviours.
|Re: Firefox & add-ons UI mockups||grbradt||3/14/12 5:19 AM|
I think a widget limited to 2 or 3 button-widths totally sucks. I
don't think users will want to click a button to get information they
now get without interaction. Not to mention a major rewrite of most of
my add-ons would be required. If it came to that, I would just abandon
|Re: [jetpack] Re: Firefox & add-ons UI mockups||Alexandre poirot||3/14/12 6:11 AM|
Can you give us some links to your addons?
It would be helpfull to bring your usecases in the discussion.
From what we have seen, all usecase we have found of "large widgets" were limited to some sort of toolbar. Like grooveshark addon which display play/pause/next buttons.
Other medium width usecases that we have seen are memory/cpu meters that can fit in 2-3 button width, and looks like something that can be displayed in a popup.
So that I'm really eager to see what is your usecase!
2012/3/14 grbradt <grb...@gmail.com>
|Re: [jetpack] Firefox & add-ons UI mockups||Alexandre poirot||3/14/12 6:20 AM|
I totally agree with you about being able to show a menu from a widget. Panels are powerfull, but it is hard to have a native look and feel. And it is especially hard to fake somekind of menu with Panel API, whereas it looks like a common usecase! (I have made multiple xul addons that display an icon in status bar which just display a menu)
About addon-bar, we clearly would like to get rid of it. I still have some doubt about that. I'm still wondering if we can put all widgets in the urlbar. Do you have same feeling? Do you have some examples? Do you think some usecases of widget will be hard to move to urlbar?
Otherwise, I really like these mockups and the way it behaves. It looks fantastic! I'm really happy to see some work being done around toolbars. I hope that it will be a win for users. i.e. having this simple cross icon in order to close toolbars, and having a clear/simple pattern to show a toolbar (click on a widget).
2012/3/13 Erik Vold <erik...@gmail.com>
|Re: Firefox & add-ons UI mockups||grbradt||3/14/12 7:44 AM|
The two I would be most concerned about are:
Canadian Weather (SDK-based)
Simple Clocks (XUL-based)
Both can be quite wide depending on the amount of data the user
chooses to display.
> 2012/3/14 grbradt <grbr...@gmail.com>
|Re: [jetpack] Re: Firefox & add-ons UI mockups||Paul Morris||3/15/12 2:22 PM|
Hi Jeff, ZER0, and everyone,
Thanks for sharing the UI mockups, they look really good!
Instead of killing the add-on bar, why not give it a nice retirement? So still an option for users, but up to them to turn it on, and move their add-ons to it. That way you're not taking customization options away.
Or at least... would it make sense to offer it as an add-on? (If that wouldn't be too meta...) I'm thinking of "Vertical Toolbar" https://addons.mozilla.org/en-US/firefox/addon/vertical-toolbar/
On limiting widget widths, I'd rather see "best UI" guidance than a hard-coded requirement. Who knows what people might come up with? Seems like a pretty big gap between 2-3 button widths and a full toolbar, (if you want something always visible). You may end up seeing add-ons that use half-full toolbars or that just string multiple widgets together, neither of which would be that pretty...
|Re: [jetpack] Re: Firefox & add-ons UI mockups||Jeff Griffiths||3/16/12 8:59 AM|
Thanks for the feedback!
When I stated previously that 'My impression was that we wanted to
No decision has been made, no secret patches exits, etc.
Another uncertainty is how ( and when ) these features will be added
|Re: [jetpack] Re: Firefox & add-ons UI mockups||Dave Townsend||3/20/12 1:02 PM|
Hey Paul, can you help me understand why you'd like to keep the add-on bar in the status area as an option in the future? I know the UX team would rather it just went away and it'd certainly be more work for us to keep it as an option in the API so I'd like to have a good idea of what cases there are where it makes more sense than just moving everything to the toolbar.
|Re: [jetpack] Re: Firefox & add-ons UI mockups||Paul Morris||3/20/12 5:43 PM|
Hey Dave, I'm just thinking about someone who had a lot of add-ons and found that the URL/main toolbar was not enough room for them all. The optional add-on bar would offer another place to put them, to keep them all visible, especially on smaller screens.
Having it also just keeps open more possibilities for what people can do with addons (especially if widgets are allowed to be wider than 2-3 button widths, but I understand that that doesn't look like the direction things are going). Since customization and user choice are things that set Firefox apart from other browsers, and people are slow to change ("Status-4-Evar" has over 150,000 users, for example: https://addons.mozilla.org/en-US/firefox/addon/status-4-evar/) ...so those might be reasons to keep it around as an option as people transition to add-ons in the main toolbar.
All of that said, I can understand the desire to keep things simple and minimize workloads. Personally I would probably avoid using the add-on bar if I could to give more screen to content... (I'm more concerned about the idea of width limits on widgets, but I suppose these things are interrelated and go together.)
(Just another thought of something to consider: the option of putting toolbars at the bottom of the window, as well as at the top.)
Dave Townsend wrote:
To view this discussion on the web visit https://groups.google.com/d/msg/mozilla-labs-jetpack/-/dZ_4QB0TqpsJ.