On Fri, 19 Oct 2007 19:01:56 -0400 DJ Delorie <[EMAIL PROTECTED]> wrote:
> > > > 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. > I think that it is a far too rigid approach. For most screensizes the current code works very well with the exporters that don't have too many options. For corner cases it might be usefull to allow for some guidance from outside. That's exactly what my patch tries to accomplish. Actually talking about tabbed window approaches. My very first attempt used a gtk notebook and it kept me forgetting to check the paper scaling option. A column per group approach may be easier on the eye in that case. Ok, back to grokking Lesstif. > > _______________________________________________ > geda-dev mailing list > [email protected] > http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev > -- $ cat .sig /dev/null _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
