Re: In the interests of standardation ...
George Bonser wrote: I sangged the below from the Caldera mailing list. It describes a method that Red Hat has come up with so that packages can add themselves to the menus of different window managers when the package is installed. It is GPLed and looks like a good idea. Debian already has the excellent menu package, that does just this. It's been around for over a year now, and about 275 packages in unstable currently use it. The basic concept is that each package contains config files that live in /etc/X11/wmconfig that define the menu entry in a generic way. The user can also override those entries in their home directory (~/.wmconfig). Check, menu is the same. (though the files go in /usr/lib/menu, /etc/menu, and ~/.menu/) There is then an app called 'wmconfig' that processes the information in all those files into window manager specific menu entries (it is a C program that is architected to be modular in nature...it can currently handle fvwm2, afterstep, and mwm style output). Ah, I think menu is better here. Menu implements a specialized programming language. You write a config file in this language, which makes it output config files for a window manager. This is more easily modified by the end-user, becuase you don't have to recompile anything. have to use some help to get that data into a config file...in RH we use fvwm2's m4 pre-processing to do it. You could hack any WM pretty easily to support this. Debian's menu package is already supported by: pdmenu (not even a window manager, just a menu program) afterstep dwww (not a window manager either) fvwm2 fvwm95 gnome icewm kde olvwm olwm wm2 wmaker The key is that the data is generic and should be easy to deal with by another external program. I'd be interested to know what data format they use. Debian's menu package is designed to use an extensible format, composed of key and value pairs. So you can very easily add new fields if you need them. -- see shy jo -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: In the interests of standardation ...
I sangged the below from the Caldera mailing list. It describes a method that Red Hat has come up with so that packages can add themselves to the menus of different window managers when the package is installed. It is GPLed and looks like a good idea. Debian already has the excellent menu package, that does just this. It's been around for over a year now, and about 275 packages in unstable currently use it. And surely the RH solution works only with X programs..! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: In the interests of standardation ...
Nicolás Lichtmaier wrote: I sangged the below from the Caldera mailing list. It describes a method that Red Hat has come up with so that packages can add themselves to the menus of different window managers when the package is installed. It is GPLed and looks like a good idea. Debian already has the excellent menu package, that does just this. It's been around for over a year now, and about 275 packages in unstable currently use it. And surely the RH solution works only with X programs..! That's a good point, the debian one can be used for X programs, text programs, and can even (if you're sneaky) bounce you out of X to run svgalib stuff and return to X when done. Oh, and it is used for menus of html documentation too.. Abritrary new typres of programs can be added easily as well. -- see shy jo -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: In the interests of standardation ...
George Bonser wrote: How do you make the debian menus work with a text display? I have never seen such a menu. What command do you run do display such a menu on a text terminal session? You use a program such as pdmenu[1], which displays menus on a text display. It's a debian package, install pdmenu and menu and type pdmenu, and you'll see it. -- see shy jo [1] I wrote it. :-) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: In the interests of standardation ...
If anyone here is known on the Caldera/Red Hat lists we should ask them to post a follow up to the original message. If we could get some element of standarization between Debian/Red Hat/Caldera it would be [IMHO] a Good Thing. Someone want to voluenteer? Adam. Internet Alaska - 4050 Lake Otis Adam Shand(v) +1 907 562 4638 Anchorage, AlaskaSystems Administrator (f) +1 907 562 1677 - http://larry.earthlight.co.nz -- On Sun, 28 Dec 1997, Joey Hess wrote: George Bonser wrote: I sangged the below from the Caldera mailing list. It describes a method that Red Hat has come up with so that packages can add themselves to the menus of different window managers when the package is installed. It is GPLed and looks like a good idea. Debian already has the excellent menu package, that does just this. It's been around for over a year now, and about 275 packages in unstable currently use it. The basic concept is that each package contains config files that live in /etc/X11/wmconfig that define the menu entry in a generic way. The user can also override those entries in their home directory (~/.wmconfig). Check, menu is the same. (though the files go in /usr/lib/menu, /etc/menu, and ~/.menu/) There is then an app called 'wmconfig' that processes the information in all those files into window manager specific menu entries (it is a C program that is architected to be modular in nature...it can currently handle fvwm2, afterstep, and mwm style output). Ah, I think menu is better here. Menu implements a specialized programming language. You write a config file in this language, which makes it output config files for a window manager. This is more easily modified by the end-user, becuase you don't have to recompile anything. have to use some help to get that data into a config file...in RH we use fvwm2's m4 pre-processing to do it. You could hack any WM pretty easily to support this. Debian's menu package is already supported by: pdmenu (not even a window manager, just a menu program) afterstep dwww (not a window manager either) fvwm2 fvwm95 gnome icewm kde olvwm olwm wm2 wmaker The key is that the data is generic and should be easy to deal with by another external program. I'd be interested to know what data format they use. Debian's menu package is designed to use an extensible format, composed of key and value pairs. So you can very easily add new fields if you need them. -- see shy jo -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: In the interests of standardation ...
George Bonser wrote: Hey! Way cool! I had pdmenu but had never used it. Now ... if only more programs put themselves into the menuing system ... :( File wishlist bugs, and upgrade to hamm, which has far more programs using it than did bo (if you're still using bo, that is..). -- see shy jo -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: In the interests of standardation ...
Adam Shand wrote: If anyone here is known on the Caldera/Red Hat lists we should ask them to post a follow up to the original message. If we could get some element of standarization between Debian/Red Hat/Caldera it would be [IMHO] a Good Thing. Someone want to voluenteer? Not me, but FWIW, I thisk SuSE has it's own version of this too -- see shy jo -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: In the interests of standardation ...
On Sun, 28 Dec 1997, Joey Hess wrote: George Bonser wrote: Hey! Way cool! I had pdmenu but had never used it. Now ... if only more programs put themselves into the menuing system ... :( File wishlist bugs, and upgrade to hamm, which has far more programs using it than did bo (if you're still using bo, that is..). Indeed, writing menu entries isn't difficult --- about thirty seconds worth of thought it all that's required. Even though this means that package maintainers should have no reason _not_ to include menu entries, this makes it entirely possible for the person filing the wishlist bug to include a suggested menu file contents -- the maintainer has to do even less thinking and is therefore more likely to include it in the next release. If someone who hasn't used menu before has to figure it out for the one package they maintain, they may not bother... Will -- | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] | | http://www.cis.udel.edu/~lowe/ | -- |If at first you don't succeed, redefine success. | | -- Taken from Hennesey and Patterson,| | _Computer_Organization_And_Design_:_The_Hardware_/_Software_Interface_ | -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
