[Fwd: Re: GemTools on remote GLASS]

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Fwd: Re: GemTools on remote GLASS]

Dale Henrichs
more list mailing problems (third attempt)... may be duplicates in the
future (sorry)...

-------- Original Message --------
Subject: Re: [GS/SS Beta] GemTools on remote GLASS
Date: Thu, 27 May 2010 08:34:45 -0700
From: Dale Henrichs <[hidden email]>
To: GemStone Seaside beta discussion <[hidden email]>
References: <[hidden email]>
<[hidden email]>

Sean Allen wrote:

>> Another  question is relative to the performance of GemTools for:        update / change / debug                 the code on remote system.
>>
>> It's valid solution or the answer times are bad ?
>
> Answer times are slow. debugging isnt pleasant. Basic update and
> change while not snappy is bearable as long as you arent doing too
> much.
>
>> There's another solutions to manage "test " on remote system  ?
>
> I do a full backup of the extent and recreate locally.
>
>>        Dario

Dario,

One solution that I haven't tried is to use VNC remotely ...

With the standard GemTools network traffic between your local client and
the remote gem corresponds to #changed: messages triggered by OmniBrowser.

With VNC the network traffic would involve updates to this display, so
it might not be faster, but it is worth trying ..

With that said, I agree with Sean that having a local test system for
doing development (based on an appliance if you don't have the extra
hardware) is very useful for resolving the "infant mortality" bugs
before introducing your changes into production.

Additionally, for remote stones, you should learn to use topaz to do
some of the routine operations ... topaz is command line based and does
allow you to do anything that you can do from GemTools like executing
smalltalk expressions and using a debugger (even browsing and changing
code .... not as nice as using a browser)...

Dale