Re: Fvwm Menu Directory
Thomas Adam tho...@fvwm.org writes: Hi, On Fri, Dec 24, 2010 at 12:31:37PM -0500, des...@verizon.net wrote: I'm getting near completion on the fvwm-menu-desktop rewrite. I thought I'd solicit some comments. Thanks, Dan. It looks good. Comments in-lined below. I tried it, seems to work OK so far. :) ... But that's not your fault -- it was like that in the original code. It just looks nasty to me. :) I appreciate most of the comments above might not relate to the work you've done, so don't think I'm picking holes unnecessarily. On the contrary, I really appreciate this, it's looking good. But it's these smaller nits that might get over-looked otherwise. Great comments, thanks! I didn't have an opinion about the prototypes but the way the whole thing is organized upside down to use them bothers me. The she-bang line needs to be changed to fvwm standard #...@perl@, it's just the way it is for testing. Same with version number. Ideally, I'd love it if this could go in CVS so it can be worked on collaboratively. I don't plan on releasing the CVS version anytime soon. I was hoping to hear it worked for at least one other person before I did that. I'll get to a commit soon.
Call for help: fvwm-menu-directory to support XDG.
Hello all, I need someone who knows perl to help me out adding XDG support to fvwm-menu-directory. As it stands this is currently broken [1]. Now, I've made some progress with this, but I don't have the time to devote to this to see it through to completion. So -- is there anyone out there who can? I'm offering the following: * Mentoring. * Help with Perl / design issues. (To minimise the impact of doing this again -- I want to see a coule of perl modules written here to support: * XDG generation. * Data gathering. * Options/wrapper around the data structure (fvwm-menu-directory itself)). I have enough time to mentor someone, give feedback for patches, etc., but not to write the whole thing. It's also a lot of work -- so be warned. The current implementation of fvwm-menu-directory is too tightly coupled with the underlying data structure, which just makes it nasty to change any of the internals -- and rip it out we must -- to support XDG. So, anyone who's serious about this, and has the time to do it, let me know off-list please and I shall set you up with what you need. If you only think you have the time, don't bother contacting me, as I might as well just carry on doing things to what I have so far -- albeit the rate of progress will be as it stands now -- slow. -- Thomas Adam [1] Read the entire thread: http://www.mail-archive.com/fvwm-workers@fvwm.org/msg01895.html -- Deep in my heart I wish I was wrong. But deep in my heart I know I am not. -- Morrissey (Girl Least Likely To -- off of Viva Hate.)
fvwm-menu-directory, xdg-menus
Hi, Fvwm-menu-directory stopped working for me a while back. I'm using FC10 right now and the script doesn't generate anything useful. I still prefer to build my own menus for the things I invoke a lot but having access to the desktop menus is nice for finding things I don't use often. Looking around, it looks like the state of KDE/Gnome menus has advanced significantly. They follow a specification called XDG. As part of ArchLinux I found a package called arch-xdg-menu that generates menus for a whole bunch of window managers including Fvwm2. It's a bit clumsy, it's not easy to find: http://aur.archlinux.org/packages.php?do_Details=1ID=10535 And when I unpack it it creates a few files and sub-directories. The only file I find useful is xdg-menu which I use like this: PipeRead 'xdg_menu --format fvwm2 2/dev/null' AddToMenu Utilities X. XDG Menu Popup xdg_menu The xdg-menu script is Perl and requires the Perl XML parser. Any thoughts on better menu builders, what we should do with fvwm-menu-directory or xdg-menu?
Re: fvwm-menu-directory, xdg-menus
2009/6/4 des...@verizon.net: Fvwm-menu-directory stopped working for me a while back. I'm using FC10 right now and the script doesn't generate anything useful. Can you be more specific? :) I still prefer to build my own menus for the things I invoke a lot but having access to the desktop menus is nice for finding things I don't use often. Looking around, it looks like the state of KDE/Gnome menus has advanced significantly. They follow a specification called XDG. Yes -- and then there's distribution-specific things (Debian has menu for instance which generates menus for FVWM amongst other WMs/DEs.) Any thoughts on better menu builders, what we should do with fvwm-menu-directory or xdg-menu? The following has been banded about for years now: http://www.cl.cam.ac.uk/~pz215/automenus.html -- Thomas Adam
