On Fri, 9 Apr 2010, Brad Jorsch wrote: > debian/README.Debian has a rationale from 1999 about why the proplist > menu format couldn't be used back then; I don't know if whatever the > problem was has since been fixed or not.
you mean this? "line that reads "OPEN_MENU" in the example above... well, it happens that appearance.menu has to be in the old format" that would be "take a file that is a complete menu definition on it's own right, and make it a submenu by inserting it into this-and-this position of this menu i am building right now", if i'm not mistaken? without having looked at it yet (time for my nap), this doesn't look impossible, or even hard (the proplist lib has code for inserting new nodes and leafs in an existing proplist). watching these files for auto-reloading of changes might be a bit tricky, but if and when we actually get there, i'm leaning towards not to do this (this may be practical if you are the only user of your desktop, but having your menu change all of a sudden in the middle of a session just because your admin has decided to install a new app, not such a good idea -- then again, we need to get there first ;). would that be acceptable? of course there's still the component that actually creates proplist-format menus from the debian metadata, but then, according to marcelo, it should be easy :) (i was eyeing it briefly since your last mail, and while i now sorta get the idea, i couldn't get it to do anything...) -- [-] mkdir /nonexistent -- To unsubscribe, send mail to [email protected].
