El 09.03.2012 13:03, Paul Seelig escribió:
On 03/09/2012 11:56 AM, Rodolfo kix Garcia wrote:
Can you send me your menu implementation to test it?
As i already wrote in the original announcement, it is available at
the
http://sourceforge.net/projects/wmlive/files download area. Here is
the
direct link to the archive (approx. 1.5 MB)) in question:
http://sourceforge.net/projects/wmlive/files/wmlive-wmaker-env_20120308.tar.gz
Thanks for your time!
Best regards
Paul
Hi,
I don't have time to do a full check but only three questions:
1. The .menu folder and your scripts are automatically copied in the
user folder? Yes? How? And... what's happend with new users?
2. The file wmaker-debian-menu-edit uses "mousepad"? What's happend if
mousepad is not installed? and gxmessage?
3. What's happend with new applications? And if one application is
removed from Debian? We should maintain the .menu files?
IMO, if you want to solve this problem, then think how to WindowMaker
should manage the root menu file. For example, if wmaker knows how to
read the WMRootMenu, why cannot edit it? Because to read, wmaker read
the file WMRootMenu, it finds "menu.hook", search the file "menu.hook"
and then, show the menu. For edit, wmaker could read WMRootMenu, search
the "menu.hook" file, copy it to $home/GNUstep/Defaults/WMRootMenu, and
then offer edit to the user. Of course, WPrefs should show a message to
the user with something like "If you edit the menu, the menu won't be
refreshed with new applications,...". When you found a new solution,
then, write it and upload it to the git.
kix
PS. The files (normally) in .menu includes this text. The upstream
loves you too :-*
# This file is deliberately empty, and serves only to get
# rid of the slightly unfortunate upstream menu layout.
--
||// //\\// Rodolfo "kix" Garcia
||\\// //\\ http://www.kix.es/
--
To unsubscribe, send mail to [email protected].
