> Right now the code is still a bit rough and only the GTK hid
> supports GUI from resource files.
"only gtk" is bad. A solution that doesn't work with all GUI HIDs is
not useful.
Now, if you made that resource part of gpcb-menu.res, and made it
OPTIONAL, that would be a bonus for gtk without interfering with
anything else (or making it difficult to add exporters without having
to edit every single GUI out there).
> Layouts can be made using vertical boxes, horizontal boxes, tables
> and frames. It shouldn't be too difficult to implement notebooks,
> but I saw no use for those right now.
IIRC we've worked on this type of problem before. A better solution
is to just put some hints in the attribute list (like a grouping tag,
or a column split tag) and let the GUI worry about how to present it.
Your .res file, for example, assumes GTK - Motif doesn't have the
concept of a "labelled box", for example.
And the way to put space between things in resource files is to put a
thing there, like we use "-" for separators you could use " " for a
gap.
You could reduce the processing by using unnamed resources:
hbox1 = {
type=HBox
test1 = {
type=VBox
padding=8
vbox3 = {
type=VBox
{HBox
{VBox
padding=8
{VBox
or use well-known names:
hbox = {
vbox = {
padding=8
vbox = {
Resources don't have to have unique names.
Also, you can convert resources to .h files (we do this for
pcb-menu.res) and embed them into the program itself.
You shouldn't need the type= as the attribute itself knows its type.
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
