Re: [Fwd: Re: GNUstep and Linux Fund]
This allows to display any menu (set via setMenu:) as the popup menu of the view. It is up to the application programmer to use or ignore this feature. Thanks for the explanation. I supposed so. So the issue is rather the default behavior; I would suggest rather do nothing on right mouse click, since that is how things work in all OSes I know of. (And the app menu is visible all the time anyway...) What do you think about that? Hans signature.asc Description: OpenPGP digital signature ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Fwd: Re: GNUstep and Linux Fund]
On 12 Nov 2009, at 16:49, hansfba...@googlemail.com wrote: This allows to display any menu (set via setMenu:) as the popup menu of the view. It is up to the application programmer to use or ignore this feature. Thanks for the explanation. I supposed so. So the issue is rather the default behavior; I would suggest rather do nothing on right mouse click, since that is how things work in all OSes I know of. (And the app menu is visible all the time anyway...) This might make sense if you are in using the Windows or Mac interface styles, but I don't really like it. Having the main menu a single click away without having to move the mouse is a good design from the point of view of usability. A menu that appears where the mouse is beats both a menu attached to the window and a menu attached to the screen in Fitts' Law terms. The difference on OS X is that most views tend to have some kind of context menu, while most in GNUstep apps don't. David -- Sent from my STANTEC-ZEBRA ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Fwd: Re: GNUstep and Linux Fund]
On 12 Nov 2009, at 16:55, David Chisnall wrote: On 12 Nov 2009, at 16:49, hansfba...@googlemail.com wrote: This allows to display any menu (set via setMenu:) as the popup menu of the view. It is up to the application programmer to use or ignore this feature. Thanks for the explanation. I supposed so. So the issue is rather the default behavior; I would suggest rather do nothing on right mouse click, since that is how things work in all OSes I know of. (And the app menu is visible all the time anyway...) This might make sense if you are in using the Windows or Mac interface styles, but I don't really like it. I think only in windows style ... since the GNUstep behavior is already the same as on a Mac. Having the main menu a single click away without having to move the mouse is a good design from the point of view of usability. A menu that appears where the mouse is beats both a menu attached to the window and a menu attached to the screen in Fitts' Law terms. Yes, the current behavior is a good thing. I actually wouldn't want it to change even when using the windows interface style, since I can see no benefit to *not* providing any action in response to a right mouse click. The difference on OS X is that most views tend to have some kind of context menu, while most in GNUstep apps don't. Yes ... it's up to the app programmer. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Fwd: Re: GNUstep and Linux Fund]
On Nov 12, 2009, at 12:00 PM, Richard Frith-Macdonald wrote: On 12 Nov 2009, at 16:55, David Chisnall wrote: On 12 Nov 2009, at 16:49, hansfba...@googlemail.com wrote: This allows to display any menu (set via setMenu:) as the popup menu of the view. It is up to the application programmer to use or ignore this feature. Thanks for the explanation. I supposed so. So the issue is rather the default behavior; I would suggest rather do nothing on right mouse click, since that is how things work in all OSes I know of. (And the app menu is visible all the time anyway...) This might make sense if you are in using the Windows or Mac interface styles, but I don't really like it. I think only in windows style ... since the GNUstep behavior is already the same as on a Mac. Having the main menu a single click away without having to move the mouse is a good design from the point of view of usability. A menu that appears where the mouse is beats both a menu attached to the window and a menu attached to the screen in Fitts' Law terms. Yes, the current behavior is a good thing. I actually wouldn't want it to change even when using the windows interface style, since I can see no benefit to *not* providing any action in response to a right mouse click. I would also point out that it is frustrating when the context menu on an OS X application doesn't also contain all of the actions that make sense in that context, such as not providing a 'Services' menu item. There's nothing more frustrating than right-clicking and not finding the action you intended to use, then having to navigate to the menu bar to find it, especially on a large screen (or in my case, multi- screen) setup. A corollary is that it is frustrating to find an action *only* in the context menu, which I have seen as well. If all actions are available somewhere on the main menu or from an Inspector panel reachable from there, providing the main menu as a default makes perfect sense, and a custom context menu just becomes an optimization of that. The difference on OS X is that most views tend to have some kind of context menu, while most in GNUstep apps don't. Yes ... it's up to the app programmer. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Fwd: Re: GNUstep and Linux Fund]
On Thu, Nov 12, 2009 at 8:55 AM, David Chisnall thera...@sucs.org wrote: Having the main menu a single click away without having to move the mouse is a good design from the point of view of usability. A menu that appears where the mouse is beats both a menu attached to the window and a menu attached to the screen in Fitts' Law terms. hmm, I'm not sure I entirely agree with this in regard to the GNUstep implementation. on OPENSTEP the menu would appear even if you clicked outside of the window there fullfilling what you say above, but under GNUstep the menu only pops up when right clicking inside of the window, meaning that it only works in Fitts' Law terms if the cursor is over a window. I can't remember the behavior of OPENSTEP when right clicking over a window for an app which is not the current active application, I would assume that it would make sense to activate the other application and display its menuForEvent: ? in the window manager i was writing, it would forward right mouse click events from the root window to the to the currently focused window, which with some modification to GNUstep i could get it to pop up the main menu, but I could never really get the mouse tracking to work, and don't really remember the details. Anyhow OPENSTEP had much more girth to the amount of space on screen where you could get the menu immediately under the mouse. I could dig up the code if anyone is interested ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Fwd: Re: GNUstep and Linux Fund]
Hi, Thanks for the explanation. I supposed so. So the issue is rather the default behavior; I would suggest rather do nothing on right mouse click, since that is how things work in all OSes I know of. (And the app menu is visible all the time anyway...) What do you think about that? Just because others do it wrong... There is also a difference in the way the interface is done. In the OpenStep style the menu is always visible, but it can be very convenient to have it right under your mouse! Especially with large monitors or for example when working with a trackpad or other pointing devices. ALso an application can choose to supply the default menu, but use the context menu only in certain areas, where it is mostly needed. This also leads to another consideration: contextual menus are exceedingly abused. In many modern applications I notice more and more that some actions are available only as a contextual menu or as a toolbar, while every action should be available and always visible (at most, greyed out) in the main menus. This is a matter of coherent application design. Contextual menus should only be a convenient shortcut. I can imagine for example an application like a vector drawing application what allows for quick inspection of the tools, or a spreadsheet the cell. However, this is application design. Usually an OpenStep application will not need it, providing an inspector palette for example. So, I'd leave things as they are. If someone needs the behaviour he can implement it. I can imagine that for example when porting an application without really wanting to adapt the interface, one can need this feature massively. Maybe we can yet another default parameter like (hide app menu con right click), but is it really worth the complication? I love to dare to be different! Also, not everything is/was windows. For example I imagine that Amiga-users will remember clicking on the workspace for a menu... Riccardo ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
