site  contact  subhomenews

Improved menu assignment

June 28, 2012 — BarryK
When a Puppy is built in Woof, or a package installed with the Puppy Package Manager (not a PET), placement in the menu has up until now been somewhat unsatisfactory.

For example, the Sylpheed .deb package from Debian Squeeze creates two menu entries, in Network and Internet categories -- the former is not appropriate. Sometimes there is no menu entry created at all when there should be.

I have given this problem some attention and made improvements to scripts 2createpackages and Woof commit:


Re: menus
Username: technosaurus
This problem was also solved in jwm_tools v0.9; however for v1.0 I am planning to implement the latest standards so we don't have to keep patching desktop files ::Note the section on %* - jwm does not activate the menu on a drag enter event or execute on a drop event, so these will get removed when the menus are created (or traybuttons, ... I just made a little hack to have jwm do pseudo-icons using a clever traybutton trick - that builds icons from *.desktop files in $HOME/Desktop/) The $HOME/Desktop idea came from reading on how to properly implement the autostart spec using jwm's StartupCommand per:

jwm drive trays
Username: zygo
"technosaurus, OK, perhaps not on the menu. Are your 'jwm drive trays' in a pet? Sounds interesting. Where can I get my hands on it?

Tags: woof