Tudor Hulubei writes:
Tudor> I think the generic implementation belongs in the toolkit, and even if
Tudor> it is present there, it should not be abused.
True.
Tudor> The purpose of my hack was to address the issue temporarily, for those
Tudor> menus that do not address it already (Options/Font & (later)
Tudor> Edit/TextProperties). All other menus do adress the problem in their
Tudor> own way (the Buffers menu is an example).
Not so. If you're talking about the way it splits buffers into
categories, I don't call this a "way of adressing the problem". If you
happen
to have many buffers in the misc submenu for instance, you'll get the problem.
> From an UI perspective, it doesn't make much sense to put
fonts in
Tudor> menus anyway.
It doesn't make much sense to have a menu with more than a dozen
entries, or one or two sub menus in general.
Tudor> To sum up, my idea was to make the Options/Font menu usable until a
Tudor> Qt/GTK port will help get rid of it.
But still, a gtk port doesn't mean that we'll get rid of the other
ports that we have already, and not all of them have this feature. So I still
think that it would be good to have this feature in Lisp. However, package
authors shouldn't have to deal with it by hand, so something like an implicit
filter would be nice.
--
/ / _ _ Didier Verna
http://www.inf.enst.fr/~verna/
- / / - / / /_/ / E.N.S.T. INF C201.1 mailto:vernaļ¼ inf.enst.fr
/_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46
75634 Paris cedex 13 Fax. (33) 01 45 81 31 19