vm team mailing list archive

[Tim Cross <theophilusx@xxxxxxxxx>]

On Fri, Mar 4, 2011 at 5:43 AM, Uday S Reddy <u.s.reddy@xxxxxxxxxxxxx>wrote:

> Dear Tim, I have added a function (vm-menubar-buttons-possible-p) in
> vm-version, which you can use to distinguish between the cases.
>
> >  While I will see what can be done, I think "punishing all the other
> users" is
> > a little strong. We are over complicating matters for very little gain
> IMO. At
> > least two of the possible toolkits (soon to be three with GTK3+) don't
> work,
> > we know two that will and then another 2 or more we have no idea about.
>
> I am not sure which toolkits you are talking about here.  Can you be
> more specific?
>
> GTK2, GTK3 and whatever the toolkit used in the NS port (Mac?)


> > Moving this functionality to use a sub-menu is not a drastic change
> really. At
> > least then we would have the same code base and same interface on all
> > platforms. The argument to keep top-level action items/buttons would
> perhaps
> > have more weight if we were referring to a frequently used operation.
>
> Yes, for anybody that uses the menubar, these two buttons would be
> among the most frequently used ones.  That is why they were made
> buttons originally.
>
>
So, what operations is it that people need frequently that require the emacs
menubar? I can see that maybe a menubar user may want the edit and possibly
the buffer menus, but the rest? If VM users need to switch to the emacs menu
frequently, I'd argue that what should happen is VM should not disable those
menu items and have them in the menubar - this would be much more convenient
that having to frequently toggle the whole menu-bar.

Tim