[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [rgui-dev] Idea for binding to the low level api
From: |
Massimiliano Mirra |
Subject: |
Re: [rgui-dev] Idea for binding to the low level api |
Date: |
Fri, 30 Aug 2002 21:54:20 +0200 |
User-agent: |
Mutt/1.3.28i |
On Fri, Aug 30, 2002 at 09:06:16AM -0600, Tom Sawyer wrote:
> > The <switch> element would represent a widget that returns a boolean
> > value. This can be the classic check button as well as the graphic,
> > animated depiction of a real switch, depending maybe on a style sheet.
> > By the same token, sections of level 1 can be a tabs in a tabbed
> > window as well as windows in a MDI application.
> >
>
> this is interesting. so instead of defining specifically the type of
> widget you want, you'd simply define the "class of widgetability", then
> a stylesheet would provide the reamining specifics. is that about
> right?
That's a very good description.
> that's very cool. just by changing the stylesheet you get a whole new
> layout, but the functionality would remain in essence the same.
And that's even better. Yes, I'm dreaming of functionality driven GUI
design.
See, I don't really want to be a GUI designer when I code anymore than
I want to be a typesetter when I write.
Once I explain what kind of input/output ports my program needs, an
engine should come up with a nice layout on its own, following some
set of good design rules, just like LaTeX comes up with a nicely
typeset document even though I only tell it that I want A4 paper, that
it is an article, and that a bunch of words throughout the text are
more important than the surrounding ones.
But I'm just dreaming...
Massimiliano
Re: [rgui-dev] Idea for binding to the low level api, Tom Sawyer, 2002/08/30
Re: [rgui-dev] Idea for binding to the low level api, Tom Sawyer, 2002/08/30
Re: [rgui-dev] Idea for binding to the low level api, Tom Sawyer, 2002/08/30