> I would have to dive into Lesstif to be able to understand the
> different approaches of both toolkits, but there must be some way to
> combine both in one definition.
The trick isn't to combine the two existing guis, but to design a
format that doesn't care about the gui. Consider when people add a
TCL/TK gui, or an Amiga GUI, or a native Win32 port. They'll want to
use the same files, but will have drastically different ways of
building the dialogs.
This is like the HTML problem - you want to describe what the content
*is*, not how it *appears*.
> > 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.
> >
>
> Could you please clarify? Instead of using a padding attribute?
For the menus, when we want to put in a separator, we just do this:
{"Export layout..." Export()}
{"Calibrate Printer..." PrintCalibrate()}
-
{"Save connection data of..." foreground=grey50 sensitive=false}
{" a single element" GetXY(press a button at the element location)
Save(ElementConnections)}
I'm suggesting that you use something like that for a horizontal
division mark, and perhaps " " to just put in some extra space between
things. I'd really rather not have anything in these files that's
measured in pixels, as those are different sizes for different people.
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
