The desktop file is hardcoded to launch Thunar, but exo-open supports "--launch FileManager" since 0.5.0.
Thinking about it, it might actually be smarter to move the desktop files that use exo-open in the exo package. For example the panel uses those desktop files in the default setup, but it does not depend on xfdesktop.
You mean the .desktop file for the menu entry? Or is that for something else?
Yes, the desktop files you have in modules/menu/menu-data/.
Hmm, well, not sure about moving them to exo, but yeah, should definitely use exo-open... xfdesktop has a soft dep on exo now, should probably make it hard.
If Xfdesktop has a hard dep on exo, moving the desktop files would be nice for the panel's default setup and it makes a bit of sense too since exo actually 'provides' the launching capabilities.
True, but it doesn't provide the menu, just exo-open. Why does the panel need it? Shouldn't it have its own default files? I'm not sure xfdesktop 4.8 is going to include all those default toplevel menu files anyway...
(In reply to comment #6) > True, but it doesn't provide the menu, just exo-open. But it is normal the modules that provides the executable also provides the desktops files, even though these are a bit special because they are used in the toplevel. > Why does the panel need it? Shouldn't it have its own default files? I'm not > sure xfdesktop 4.8 is going to include all those default toplevel menu files > anyway... The new panel has a feature to load desktop files from the application pool (ie. all the apps in the default menu), this makes the default configuration a lot easier and more powerful. Of course i can also hardcode this, but if one of the panel dependencies provides files that can be used in the default setup, then why not...