Questions:
1.) The above files produce a single wbar opera icon labeled “Opera_browser-only”. What is the rule for which “.desktop” entry is used to label the icon?
2.) How can a separate icon for each “.desktop” file be created?
3.) The “.desktop” files produce menu entries under a parent menu item labeled opera10 under the Applications main menu item.
a. What is the rule for what the parent menu item is labeled (opera10)?
b. What is the rule for what the order is for sub-menu items?
c. How can a new main menu category be created and used for application extension menu entries?
For instance "My tools" instead of "Applications".
I setup the "~n.desktop" to be used to maintain existing submenus in legacy window managers. It is not supported by freedesktop WMs/DEs.
1. Only the "base", i.e, sans ~n.desktop is used for wbar, otherwise wbar would be overrun with duplicate icons. This is how is was deployed in prior 2.x version using JWM/Wbar specifications.
2. Currently not supported for legacy window managers. If separate icons then assumed separate applications. Rememeber we want to maintain support for legacy WMs. Tiny Core is not going to become Tiny Core/LXDE.
3a. If any ~n.desktop is found then the 'base' one is used to create parent menu item.
3b. By the numercial order 1 then 2 then 3 then ...
3c. 'Applications' is a fixed target used by the system, again for legacy WMs. If using a freedesktop supported WM/DE, then you can use the Categories field as defined, supported and deployed by the freedesktop WM/DE, examples see LXDE or XFCE extensions.