gEDA-dev: HID interface from resource files

[DJ Delorie]

> > This is like the HTML problem - you want to describe what the content
> > *is*, not how it *appears*.
> 
> To stay with the HTML analogy, IMHO the HID_Attribute struct
> contains the content, the resource is the CSS to spice things up.

Except that in our case, things like "hbox" and "vbox" are appearance
tags.  We'd use something like "group" to say how attributes are
related, and let the GUI organize them.  Win32 might use a tabbed
multi-window, for example, Motif might use a work area with a menu to
select groups.