Creating a GUI

if it's exposed to glade then they will show in the glade editor ( as long as you start the editor as I said before )
other wise no, you would have to look at the source.
We will need to make a separate advanced gladeVCP manual

if we want to promote building GUIs we should ask one of the MAKE script experts to add --install_screen to MAKE
like we do for installing comps


If you get time make a glade panel that represents a DRO widget - it doesn't have to work.
I will tinker to see if I can make it a gladeVCP widget.

One other way of piggybacking GUIs is to add the regular GUI in the DISPLAY= section
and loading the other one from hal
in the HAL section of the INI file
add HALCMD = loadusr gaxis

this is how gscreen does it in the sample configs and works well when developing a screen when not everything works yet (you can use the other screen to do whats missing)

Here is some code that I used to have TOUCHY use a local (in the config's folder) glade file if available
or else use the regular one.

You could use this same idea to have your screen load the local one then you could have a different screen on each config just by having a different glade file in it.
Also makes it so you don't have to search all over for the glade file...
just another idea.

d = os.environ
localglade = os.path.join(d,"touchy.glade")
if os.path.exists(localglade):
print "\n**** TOUCHY INFO: Using local glade file from %s ****"% localglade
self.gladefile = localglade
else:
self.gladefile = os.path.join(datadir, "touchy.glade")
print"\n**** TOUCHY INFO: using glade file from: %s ****"% datadir
self.wTree = gtk.glade.XML(self.gladefile)

i would think box or frame would be best.. it you right click a container you can force it to be a top level object.
but I can fix that later anyways.

oops that environmental variable INI_DIR is not available...I'll find another way to get the config path...