[REBOL] Re: Fwd: Re: Re: RFC: Rebol Framework
From: robert:muench:robertmuench at: 25-Sep-2002 17:39
> -----Original Message-----
> From: [rebol-bounce--rebol--com] [mailto:[rebol-bounce--rebol--com]]
> On Behalf Of Petr Krenzelok
> Sent: Wednesday, September 25, 2002 2:39 PM
> To: [rebol-list--rebol--com]
> Subject: [REBOL] Re: Fwd: Re: Re: RFC: Rebol Framework
> OK, I am starting to understand, where all the concept leads,
> although I will wait for some results.
Hi, ok. First try will most likely use the finit-state-machine (FSM)
from Gregg.
> I also read http://www.nakedobjects.org/introduction.html , but I have
to
> say, that from my experience I don't fully agree to automatic UI
generation.
Same with me. And I like a lot about nakedobject but not the GUI part.
I'm not sure about drag & drop either. I'm more using my keyboard to
work fast. I'm more in th Norton commander league :-)). I'll like the
clear approach to create a direct relation between data-objects and
screen representations. Anyway, we just take what
makes sense.
> I would prefer whole framework to function as repository of
> objects, all their logic and relation, and not trying to guess what is
the
> best way for user to see his/her data presented.
Mostly agreed.
> how will you represent block? Will it be combo-box, list-box, or more
> complicated grid? You want list, I want grid - what then? :-)
You take grid, I take list ;-)) that's my goal. There is no direct link
between data and screen representation. Sometimes grid makes sense,
sometimes a list. It depends on the decision you want to make and what
kind of support data you need.
> btw: what about access rights aka roles? Will it be possible
> to define some via rules? :-) How engine will work with them? Eh,
can't
> wait for for rules to work :-)
IMO access rights are just that: rules. A role is more like a container
for a set of rules ;-)). You see what I mean... Robert
