Re: Dreaming About Redesigning SQL

"Mikito Harakiri" <mikharakiri_at_yahoo.com> wrote in message news:bdf69bdf.0310261833.1177652_at_posting.google.com...
> "Bob Badour" <bbadour_at_golden.net> wrote in message
news:<ebCdnSNkie3aygGiU-KYhw_at_golden.net>...
> > "Mikito Harakiri" <mikharakiri_at_iahu.com> wrote in message
> > news:AVUmb.3$uD6.177_at_news.oracle.com...
> > > From practical perspective, I find it odd that one can't describe GUI
> > > relationally. This is why we still use old procedural languages on
client
> > > side, right?
> >
> > One can describe anything relationally. What makes you think it
impossible
> > to describe a GUI relationally?
>
> I must correct my statement, of course: So far nobody succeeded doing
> so.
>
> Application developers routinely describe GUI like this:
>
> <table>
> <tr>
> <td>
> User:
> </td>
> <td>
> <input type="text" name="usr" value="<%=usr%>">
> </td>
> </tr>
> <tr>
> <td>
> Password:
> </td>
> <td>
> <input type="password" name="pwd" value="<%=pwd%>">
> </td>
> </tr>
> </table>
>
> which is just 4 GUI elements in 4 cells layout table, and this
> approach proved to be quite sucessfull. For comparison, try describung
> this trivial GUI page in relational to see what I mean.

What's difficult about that? It's just two tuples. Received on Mon Oct 27 2003 - 04:00:47 CET