Re: [Ayatana] Persistent menu mockup
I think this is the best solution I have seen. I particularly like the application icon being transparent beneath its title. I do have two concerns. - What happens on small screens when the menu overlaps with the title. - I would feel much more comfortable with title on the left hand side, but maybe the title being on the left would provide a nice way for windicators to be clearly associated with their application. If/when we get windicators. Overall I suspect the windicator implementation is going to have a significant effect on the global menu. ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] Persistent menu mockup
That looks great, and solves most of everyone's complaints with the current hidden global menu. I do have one concern: what happens to the window controls when the window is maximized? you could scoot the menu over a bit, but then, that might look odd for non-maximized windows. Other than that though, I'd love to see this, as it's a viable contender. On Wed, Apr 20, 2011 at 10:50, S. Christian Collins < s.chriscoll...@gmail.com> wrote: > Hi folks, > > Many people have mentioned the problems with the inconsistency of the new > panel (menu only visible on hover, etc.). Here is my proposed solution to > this problem: > >- The menu of the active window is always displayed in the panel. >- The title of the active application is displayed on the right side of >the panel, just to the left of the system tray. >- There is a clear division in the panel between the application title >and the system tray to visually link the window's title with its menu. >- The application's icon is displayed transparently beneath the window >title for at-a-glance identification of the active window. This would make >it easier to tell which window is currently active. >- If the active window's menu is long enough to drift into the >application title, the title would simply fade out at its leftmost edge >(similar to its current behavior whereby the title fades at the rightmost >edge when the menu appears). > > Have a look at my mockup and decide for yourself: > > > > -~Chris > > ___ > Mailing list: https://launchpad.net/~ayatana > Post to : ayatana@lists.launchpad.net > Unsubscribe : https://launchpad.net/~ayatana > More help : https://help.launchpad.net/ListHelp > > -- Ian Santopietro "Eala Earendel enlga beorohtast Ofer middangeard monnum sended" Pa gur yv y porthaur? Public GPG key (RSA): http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search=0x412F52DB1BBF1234 ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
[Ayatana] Let's have the launcher phagocytize the new system tray
Hey, I have an idea. Maybe this was discussed here before; if it was, I'm sorry. There was an ayatana thread here discussing a short-term solution for e-mail in Ubuntu. One thing I particularly remember from it was something about duplication of effort when it comes to shortcuts and how to access features; since the launcher now has an API, you can click on the messaging menu or right-click on evolution icon in the launcher, etc. Well, this inspired me. Do we really need the system tray when similar things can be achieved through the launcher now? Picture it: Instead of using the launcher icon to launch / focus Clementine *and* the sound menu to control it, why don't we have the sound menu functions embedded into Clementine right-click menu? Or, instead, why don't we have an icon in the launcher with the same functions the sound menu currently has? The same goes for, say, Transmission (when not launched, right-clicking would only show regular menu; after it's launched, right-click would show indicator menu), Ejecter (I'm currently using it, that's why I had the idea), keyboard layout, messaging menu... Everything! Me menu could then mix up with the messaging menu (something that has been discussed here) or become a lense. Shut down button, with all its options, could also become an icon in the launcher (something not removable, like the rubbish bin is right now). I guess it would be better to keep the clock in the panel, though. I'm not a coder, so I don't think how feasible this is, but I want to emphasise that all the work put in the appindicator thing wouldn't be wasted, since all the information provided through it would just be redirected to the launcher. I guess not a lot of code would have to be written to hook these things up, am I right? Upstream applications wouldn't need to adapt anything; their code right now would work with any implementation of indicators, be it on classical 2D gnome or in Unity. I don't know, but I think this is neat, what do you think? =) *Peterson* *http://petercast.net* ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] Persistent menu mockup
Is this windicator thing still going on? How are things progressing on that matter? (sorry for drifting away, I'm just very curious about it) *Peterson* *http://petercast.net* On 20 April 2011 14:03, Elias K Gardner wrote: > I think this is the best solution I have seen. I particularly like the > application icon being transparent beneath its title. I do have two > concerns. > >- What happens on small screens when the menu overlaps with the title. >- I would feel much more comfortable with title on the left hand side, >but maybe the title being on the left would provide a nice way for >windicators to be clearly associated with their application. If/when we get >windicators. > > Overall I suspect the windicator implementation is going to have a > significant effect on the global menu. > > ___ > Mailing list: https://launchpad.net/~ayatana > Post to : ayatana@lists.launchpad.net > Unsubscribe : https://launchpad.net/~ayatana > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] Persistent menu mockup
My compliments, what a brilliant idea. It needs some more thought, but in my opinion this is the best solution as of yet. Especially as it is quickly recognizable which window the menu belongs to. On Wed, Apr 20, 2011 at 7:03 PM, Ian Santopietro wrote: > That looks great, and solves most of everyone's complaints with the current > hidden global menu. I do have one concern: what happens to the window > controls when the window is maximized? you could scoot the menu over a bit, > but then, that might look odd for non-maximized windows. Other than that > though, I'd love to see this, as it's a viable contender. > > On Wed, Apr 20, 2011 at 10:50, S. Christian Collins < > s.chriscoll...@gmail.com> wrote: > >> Hi folks, >> >> Many people have mentioned the problems with the inconsistency of the new >> panel (menu only visible on hover, etc.). Here is my proposed solution to >> this problem: >> >>- The menu of the active window is always displayed in the panel. >>- The title of the active application is displayed on the right side >>of the panel, just to the left of the system tray. >>- There is a clear division in the panel between the application title >>and the system tray to visually link the window's title with its menu. >>- The application's icon is displayed transparently beneath the window >>title for at-a-glance identification of the active window. This would >> make >>it easier to tell which window is currently active. >>- If the active window's menu is long enough to drift into the >>application title, the title would simply fade out at its leftmost edge >>(similar to its current behavior whereby the title fades at the rightmost >>edge when the menu appears). >> >> Have a look at my mockup and decide for yourself: >> >> >> >> -~Chris >> >> ___ >> Mailing list: https://launchpad.net/~ayatana >> Post to : ayatana@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~ayatana >> More help : https://help.launchpad.net/ListHelp >> >> > > > -- > Ian Santopietro > > "Eala Earendel enlga beorohtast > Ofer middangeard monnum sended" > > Pa gur yv y porthaur? > > Public GPG key (RSA): > http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search=0x412F52DB1BBF1234 > > > ___ > Mailing list: https://launchpad.net/~ayatana > Post to : ayatana@lists.launchpad.net > Unsubscribe : https://launchpad.net/~ayatana > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] Fitts Law
On 19 April 2011 18:24, Mitja Pagon wrote: > - "Matthew Paul Thomas" wrote: >> >> It does. In the videos I watched of Charline Poirier's user test two >> weeks ago, of the eight out of ten people who could find the hidden >> menus at all, seven of them discovered the menus while mousing over the >> close/minimize/unmaximize buttons in a maximized window. >> >> They then concluded that the way to access menus was to hover over the >> close/minimize/unmaximize buttons, and then move sideways. This was very >> slow, and didn't work at all in unmaximized windows. >> >> People were much faster at using LibreOffice's menus, which are not yet >> integrated into the global menu bar by default. >> > > The question remains. Why, despite being a definite usability regression, is > the menu still hidden? Who makes this decisions and why can't they accept > the fact they are wrong in this case? > > Cheers, > Mitja > These questions really need answering, You don't need to be a usability expert to see there are very real problems with the panel/menu implementation in Natty. The frustrating thing is that we could revert either the merging of the titlebar OR the global menu (keeeping merging for maximized windows) and come out with something reasonably sane. If even MPT thinks things are broken then why are we continuing with the current mess? You think Apple or Microsoft would ship with something as ill thought out as the current panel design? I thought we were supposed to be bettering OSX? All I'm seeing in the panel is OSX plagiarism mixed in with our own essence of usability WTF. Luke. ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] Fitts Law
2011/4/20 Luke Benstead : > If even MPT thinks things are broken then why are we continuing with > the current mess? You think Apple or Microsoft would ship with > something as ill thought out as the current panel design? I hate to point this out, but the ratio of Canonical:community e-mail addresses on this list seems heavily weighted on the side of the community. This means that there is an awful lot of noise and discussion, and - as far as I can tell - little to no direction, input or explanation from the People Who Make The Decisions. I do hope communication will improve. This just seems to be, in the most part, a vacuum outlet for community discontent, rather than a place for constructive discussion. I've also noticed this in bug reports relating to design decisions made by Canonical, or in Ayatana projects. -- Toby Smithe ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] The top right thing
I'd call it the power button. From: Jim Campbell To: ayatana@lists.launchpad.net Sent: Monday, April 18, 2011 5:20 PM Subject: Re: [Ayatana] The top right thing The documentation team is wondering what to call the power-looking icon in the top right of the screen. Someone started a thread to discuss the matter using the subject, "The top right thing." I doubt the Ayatana folks would like us to refer to it as "the top right thing." Is there a preferred term for this button? (It is the one that provides access to power settings, log-out, switching users, activating a guest session, and system settings.) Thanks very much, Jim ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] Persistent menu mockup
Without explaining what is your idea for maximized windows, the usefulness of the mockup is very limited. Most people would agree that making the menubar moving left and right is not an acceptable solution, so explaining what would you do in the maximized case is essential. Le mercredi 20 avril 2011 à 11:50 -0500, S. Christian Collins a écrit : > Hi folks, > > Many people have mentioned the problems with the inconsistency of the > new panel (menu only visible on hover, etc.). Here is my proposed > solution to this problem: > * The menu of the active window is always displayed in the > panel. > * The title of the active application is displayed on the right > side of the panel, just to the left of the system tray. > * There is a clear division in the panel between the application > title and the system tray to visually link the window's title > with its menu. > * The application's icon is displayed transparently beneath the > window title for at-a-glance identification of the active > window. This would make it easier to tell which window is > currently active. > * If the active window's menu is long enough to drift into the > application title, the title would simply fade out at its > leftmost edge (similar to its current behavior whereby the > title fades at the rightmost edge when the menu appears). > Have a look at my mockup and decide for yourself: ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] Persistent menu mockup
On 04/20/2011 11:41 PM, Conscious User wrote: Without explaining what is your idea for maximized windows, the usefulness of the mockup is very limited. Most people would agree that making the menubar moving left and right is not an acceptable solution, so explaining what would you do in the maximized case is essential. Why couldn't the same solution work for maximized windows as well? The only difference being the presence of the close, minimize and maximize buttons to the left of the global menu when a window is maximized. Sure, this would cause the menu to shift over to make room for the window buttons, but would this really be so much of a distraction to people? -~Chris ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] Persistent menu mockup
On Wed, Apr 20, 2011 at 11:41 PM, Conscious User wrote: > > Without explaining what is your idea for maximized windows, the > usefulness of the mockup is very limited. > > Most people would agree that making the menubar moving left and > right is not an acceptable solution, so explaining what would > you do in the maximized case is essential. I don't see the problem. When a user maximizes a window she/he would already expect a change in the position of the menu if there weren't a global menu. Further, all maximized windows have the same menu position, so there's no inconsistency between windows. ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
