On Sat, 10 Apr 2010, Carlos R. Mafra wrote: > > in this arena, i would kill this thing altogether, then embrace and > > extend carlos' wmgenmenu idea. it needs to be extended a bit so you > > can specify app labels in a gettextable way (ie instad of "oowriter
> The idea of killing all those old pre-defined menus and generating > them on-the-fly with wmgenmenu at wmaker.inst time is nice > (and I had thought about it too but haven't tried implementing it) > > I think the "extension" could be worried about at a later stage. it's not complicated, just needs a bit of pressing the right keys in the correct order ;) i'll whip this up in the weekend. > Agreed about the "fallback". And having apps in the menu which are > guaranteed to be in your PATH is way nicer than having a menu > containing "Netscape like" kind of oddities. > > So I really think that having a centralized menu generator is much > more beautiful and general than having all those outdated menus. > But this will require some effort, I guess. not much. minimal changes to wmgenmenu, and some mods to wmaker.inst. and i'll have the pleasure of killing 8k lines of... trash :) > And regarding the "old" menu, does the debian menu stuff require it? it seems that for now yes (brad is making good progress explaining me what this thing actually is, but i'm not very smart, and learn slow). at the moment it seems we will be able to kill it, but it will require a bit of an effort. > If not, let's kill it and use proplist-only menus. -- [-] mkdir /nonexistent -- To unsubscribe, send mail to [email protected].
