>That brings us to the point of -- "What is a proper XDG_* 
>environment for
>trinity?" Right now in tqtinterface, we have complete control over 
>the XDG
>environment with trinity.sh. I currently have:
>
>What additional can we do/(do better) with the environment setup?

As I wrote previously, Debian based distros do not use 
/etc/profile.d. We need to explore how to modify the XDG_*variables 
without using /etc/profile.d.

>+1 When I was shopping desktops, it was not uncommon to have kde3, 
>kde4, wm2
>fvmwm2, e-16, e-17, gnome, fluxbox, twm, blackbox, openbox, etc. 
>all installed
>simultaneously. The only real havoc was caused by kde3/kde4/gnome. 
>That's why
>the X11 project put out an entire menuing standard to handle what 
>is isn't
>visible in each desktop. I've picked through the standard, but 
>never compared
>between what we have and what is says. Further, in doing so, I 
>don't ever recall
>seeing a clean way of preventing the kde3/kde4/gnome menu mess. It 
>is almost as
>if there is a need for a global 'menuedit' to manage /etc/xdg/menu 
>on a global
>and per/user basis to include/exclude apps in menus when multiple 
>desktop environments are installed.

The menus we now install work well enough within Trinity. We have 
the option to compile with a "[KDE]" suffix. To reduce menu clutter 
from duplicate naming, the default Trinity menu places all KDE menu 
items in a separate "KDE" submenu. We also have an alternate menu 
that must be installed manually that excludes all KDE menu items. 
We probably should have a GUI option somewhere to swap those two 
menu options.

The menu mess begins outside of Trinity.

Darrell