Re: info.el should use easymenu
>>>> "-BP" == William M Perry
<wmperry(a)aventail.com> writes:
-BP> Hrvoje Niksic <hniksic(a)srce.hr> writes:
> I don't see a good reason to promote easymenu in that
fashion.
> Currently XEmacs supports the new add-{submenu,menu-button}
> functions and the old add-menu. When an external package
> desires FSFmacs compatibility, it's free to use easymenu.
-BP> I don't think easymenu is any harder to use than the raw
-BP> stuff, unless you do some weird things like VM or Emacs/W3
-BP> with the user able to specify using only some of the
-BP> available menus.
This in _not_ weird, it should somehow be made automatic, with a
reasonable default subset of normal XEmacs menubar automatically
inserted and that customizable by the app and by the user if desired.
Look at PSGML to see the possible lossage; I need a 150 column window
to get it all visible....
There should be a documented set of standard submenus (File, Mule,
Options, ..., maybe some lower-level ones like Custom, too) with
documented minimum contents to make user customization easier.
This has been on my to-do list for a while, but I never got around to
understanding VM _and_ W3 _and_ easymenu so that it could be done with
as little impact on existing code as possible. So sorry!
-BP> I didn't realize stock easymenu forced you to have a copy
-BP> of the menu on the popup-menu - that is incredibly bogus UI.
:-(