>> On 02/29/2012 12:56 AM, Rodolfo García Peñas wrote: >>> On Tue, 28 Feb 2012, Paul Seelig escribió: >>> If somebody donate money in the wmlive project >>> homepage, please, share it with me ;-) >>> >> No problem! ;) > > Send "my" money to the Debian project. > Well, in this case i'd rather keep it, as Debian already gets the code of both of us. Personally, i can't feed only based on idealism, and i can't produce code if i am not sufficiently fed. As you can see, there indeed is an existential limit to altruism. ;)
On 02/29/2012 06:58 PM, Rodolfo kix Garcia wrote: > http://lists.debian.org/debian-mentors/2012/02/msg00617.html > http://lists.debian.org/debian-devel/2012/02/msg00961.html > Oh great, you are already trying to find a proper solution, just the way i am envisioning it myself! No answers, though, not even on debian-devel. > I don't know how to remove "Applications/" form the wmaker-method script > (doing it in the correct way) > Maybe some dirty sed tricks at the resulting menu file might be the only way to work around this? But then again i haven't looked any deeper into this yet. So much to do, and so little time... > xdg should be dropped from wmaker. wmaker menu works fine. > While wmgenmenu works remarkably fine, and indeed does get the submenu nesting levels perfectly right, it doesn't take into account software packages it doesn't "know" about. Therefore i still see a need for wmaker xdg menus in context of Debian. For example, on wmlive, it doesn't create any entries for the gnome-terminal, which is both present and used by default. It only creates an entry for xterm, which in wmlive is not used for anything at all. I much prefer some kind of menu generation which takes into account what software is actually available on the system, instead of choosing only a subset of available programs based on some limited assumptions. Maybe there could be found a way to remedy these limitations? Another problem is that, unfortunately, proplist menus can't include any other proplist submenus, which is a true pity. But this is probably a different, and not directly related issue. > IMO, we should work together. If the wmaker packages are fine, the > wmlive work probably can be packaged in a new package. Then, downloading > the iso, adding the wmaker packages and the wmlive package with the > configuration, is the better way to do it. > We already started working together long time ago. ;) As you are saying, the best approach is to merge these things together, in order to avoid duplicate efforts. Nonetheless, i am still working on the stuff i'd like to present as a first suggestion for a merge, so it will still take some time for me to present a viable first approach. Thanks, Paul -- To unsubscribe, send mail to [email protected].
