dswd
commented
12 years ago With Swine I try to not use the normal menu entries that wine normally creates. The main reason for that is that windows programs are pretty messy with menu entries and create lots of them even for their webpages, readme files, and uninstall routines so that I simply don't want them mess up my menus. Also these automatically created menu entries are not organized by slots and have the slot embedded in the wine command line which is must be parsed and is very fragile when the wine developers change their code.
Swine can create shortcuts for all windows menu entries (actually all .lnk files found in the prefix). Swine has a context menu button that will create shortcuts for windows menu entries and will also prompt for that after running a program by hand. These shortcuts will be exported and imported along with all the files belonging to the slot.
Additionally, Swine can create kde/gnome menu entries for shortcuts and has context menu buttons for that. Currently these entries are not included in slot archives so this should be changed. Also Swine currently lacks the ability to create desktop entries for shortcuts, I will have a look at this as well.
How about that?
It would be a nice feature if all menu entries belonging to a specific slot could be imported and exported together with the wine prrefix. This could be extended to desktop symbols as well. As far as I know, menu entries are stored in the following places: .config/menus/applications-merged/wine .local/share/applications/wine .local/share/desktop-directories/wine* .local/share/icons