[EMAIL PROTECTED] wrote:
> > > I assume REBOL/View can work as a client to REBOL/Command. REBOL/View
> > > being a visual version of REBOL/Core and REBOL/Command being a binary
> > > executing version of REBOL/Core (amongst other things).
> > >
> > > Am I on the right track here? Will REBOL do this?
> >
> > The only one question is what do you expect of REBOL/View gui. I would
> > still more like to see /Core's multitasking ability than being dependant on
> > /Serve, /Command and having to launch yet-another-rebol from harddrive.
> >
>
> Yes, /View is the big question now. Basically /View would need to present
> graphical represention of a building with buttons on it. When you push a unlock
> door button, /View would send the request to the server (/Core, /Command, or
> /Serve) that would handle the request. Some method of accessing controls not
> in immediate view would be nice, like multiple pages or scroll bars.
>
It can be done imho in current state of things. However, I don't understand that
client/server aproach. What I need is ability to load View as a component to
/Command version, or just tasking/threading together with shell execution moved to
/Core (/View). I would like to see REBOL being more async, as /View's capability of
multiple windows is nice, but what for, if we are e.g. downloading some image to
one window, the behavior of REBOL is its blocked state.
> Another thing is a way to put /View into a kiosk (full screen no escape) mode.
> However I am sure RT would add this functionality without too much lobbying.
Hmm, you can take the whole screen. It's there from beta 2 IIRC.
Anyway, we should move such discussion to Ally list ....
-pekr-
>
>
> --Ryan
>
> >
> > -pekr-
> >
> > >
> > >
> > > --Ryan
