On Wed, 29 Sep 2010, Tamas TEVESZ wrote:
> about this menu thing that pops up every now and then -- i may be
> misunderstanding something, but i just came by some code pieces in
> src/defaults.c that do what looks like prepending, appending, and
> otherwise stuffing plain good old proplist menus to one's root menu.
>
> in ${prefix}/etc/WindowMaker (SYSCONFDIR/GLOBAL_DEFAULTS_SUBDIR) have
> a file named GlobalMenu.post (GLOBAL_PREAMBLE_MENU_FILE) with contents
> like this:
> restart, and observe the bottom of your root menu.
>
> does that not solve half the problem with including debian menus and
> suse menus and altlinux menus and whatnot menus?
ok, so a problem with that is that it's not entirely voluntary, but
with the patch i just posted, including proplist menus becomes
possible.
the thing is... i've wanted to do this for quite some time now, and
now that i finally managed to chew through, i forgot *why* exactly did
i want to do this.
removing old menu support and running shit through cpp became a sort
of an obsession of mine, but since up until about 10 minutes ago that
was the only way to include other menus, the idea was shelved.
now that it's no longer an obstacle, that crap can all be removed, but
first replacements for stuff like the debian and redhat and whatever
menu generators need to be written.
and here's the deal: can someone give me a rundown how do these things
actually work? i played with debian's thing a couple of days ago when
bento last brought the subject up, but i didn't get very far.
basically, as far as i can tell, debian has app definitions in its own
format, and then **magic**, and then it becomes the old-style menu in
/etc/X11/WindowMaker/menu.hook or thereabouts.
what happens in the **magic** part? (also, how do other distros do
this?)
--
[-]
mkdir /nonexistent
--
To unsubscribe, send mail to [email protected].
