On Fri, 19 Oct 2007 18:06:03 -0400
DJ Delorie <[EMAIL PROTECTED]> wrote:
>
> > 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.
>
Yeah, but you have to define some common denominator to describe an
interface. I believe the layout types I have defined now can be
implemented in most toolkits or emulated in one way or another (RowColumn
widget?).
Only for toolkits that only use fixed XY positions for widgets I foresee some
problems.
> 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.
>
> > > 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.
>
Ok, and define the space to be a fixed amount of padding. Agreed, that does
give a more consistent interface throughout the application.
>
> _______________________________________________
> geda-dev mailing list
> [email protected]
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
>
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
