Re: Dreaming About Redesigning SQL

From: Mikito Harakiri <mikharakiri_at_yahoo.com>
Date: 27 Oct 2003 18:13:07 -0800
Message-ID: <bdf69bdf.0310271813.5b8dd407_at_posting.google.com>


"daveb" <davebest_at_SuPsAaM.net> wrote in message news:<0hhnb.86942$Ms2.47872_at_fed1read03>...
> "Mikito Harakiri" <mikharakiri_at_iahu.com> wrote in message
> news:sUbnb.19$nM4.107_at_news.oracle.com...
> > You have
> > to specify 2-dimensional spatial relations among the GUI elements, and this
> > is where the problem becomes serious.
> >
> Why? The spatial relationships are just data that are fed to a layout
> engine, and can be represented as tuples: e.g. absolute x, y positions,
> position relative to another widget, or geometry specifications (snap to
> edge, etc). Absence of layout is just a directive to use defaults, as in
> the example above.

So, how would you specify GUI in the example above as a data? I need to lay out 2 prompts and 2 input widgets inside table cells (that implicitly specify grid layout).

Next, assume we have a table widget and it doesn't fit into a screen. Then, a scrollbar appears. Is a scrollbar a part of "relational" GUI model or not? Received on Tue Oct 28 2003 - 03:13:07 CET

Original text of this message