Hello Nick,

So then the cut-point is at the level of message sends between the GUI and the model?

How are events handled (messages from the model to the GUI) ... this is the spot where I think that OmniBrowser (in the GLASS implementation) started to falter ... there a large number of event messages that end up with more network round trips than one would like ...

It seems that there is a need for some sort of "message concentrator" that cuts down on network round trips, but this is wandering into "early optimization" territory:)

I think it would definitely be interesting to give this a try with GemStone as it has the potential to provide much more flexibility in terms of which GUI components can be used ....

Dale
On Apr 27, 2011, at 1:27 AM, Nick Papoylias wrote:

Hallo Dale,

In terms of remote tools, we are working with rST which is still kind of unstable but still
useful in many cases. Hopefully in your case too.

http://www.squeaksource.com/@69jY6Xu1NHtRD19j/lOHxDstw

So if your scenario is this:

You already have or you are creating a tool with Model-View architecture
that plays well when tested locally on a client and you want to go remote.

Then with rST (hopefully) you just wrap your model in a network proxy and everything plays out of the box remotely.

At least this is our goal.. we are currently working with remote reflection (in a more theoretical sense) but
we should and will find time to make rST more robust for the community.

I hope this helped, a bit.

Nick

On Wed, Apr 27, 2011 at 3:23 AM, Dale Henrichs <dhenrich@vmware.com> wrote:

On Apr 26, 2011, at 5:27 PM, Tudor Girba wrote:

> Hi Dale,
>
> On 27 Apr 2011, at 02:22, Dale Henrichs wrote:
>
>> On 04/26/2011 05:01 PM, Tudor Girba wrote:
>>> Hi Dale,
>>>
>>> Glamour is independent from the rendering, just like Omnibrowser is. Here is a short description:
>>> http://www.themoosebook.org/book/internals/glamour/rendering
>>>
>>> We already have a working Seaside rendering code for the basic widgets of Glamour. For an example, take the following steps:
>>>
>>> 1. download
>>> http://hudson.moosetechnology.org/job/moose-with-glamour-seaside/lastSuccessfulBuild/artifact/moose-seaside/*zip*/moose-seaside.zip
>>>
>>> 2. run:
>>> WAKom startOn: 8081
>>>
>>> 3. go to:
>>> http://localhost:8081/moose/metaBrowser
>>>
>>> Cheers,
>>> Doru
>>
>> I'll hold off exploring the scope of the Glamour port until I see if Glamour can be used to construct the configuration wizard:)
>>
>> I'm not skeptical as much as I am very busy...
>>
>> Did I provide you with enough info for the use case?
>
> Not really :).

okay?