Jiri Srain <jsrain@suse.cz> 07/09/07 2:57 AM >>> What I do not like on the YaST-gnome.menu file as it is in SVN is that it contains all possible groups. This cannot work for 3rd party modules. I hope that there is a way to workaround this, but it is not obvious to me (without reading the standard properly).
Yes, customization by additional modules (3rd party or system) is built into the .menu spec. To add to or modify <name>.menu file, modules install their own additional .menu files into <name>-merged directory. These menu files are then automatically merged into the top level menu.
Another problem (apart already mentioned translations handling)
is that for YCP we do not have a XML parser which would be able parse the .desktop files.
The translation handling is also built in the .menu spec and is handled the exact same way that translations are handled in .desktop files. hrmm, the YCP module is already parsing .desktop files today correct? , do you mean .menu files. Sorry for my lack of knowledge about how KDE generates it's top level menu but as it uses the .menu spec would it be possible to tie into the library it uses. Thanks. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org