> 
> Squeak has Monticello for this, I can live without it as I'm
> developing alone. From the list I get the impression that it doesn't
> scale well, the people preparing the next image seem to have serious
> performance problems.

Even for my one person project I cannot live without MC. And it is 
scaling well (even if has some speed problems and missing atomic load) 
but managing Squeak with MC is not a simple project, but we are making 
it real :)

> 
> KF> 6.  I'll periodically run my application to see how its working from a
> KF> user perspective.  Generally that application starts from a known state
> KF> and at a known entry point.  The start up state may differ slightly
> KF> based on saved information.
> 
> Every now and then I file all sourcecode into a fresh image to make
> sure that I didn't do something that depends on my interactively
> creating some objects. I don't think this is necessary and still is a
> relic from having to be able to compile some source and start a
> program with a well defined entry point.


Run your tests too :)

> 
> Actually I believe in Squeak it doesn't matter how objects are
> created. You deploy an image which contains all necessary objects and
> you don't need a single entry point which will set up everything ready
> to use. I still believe such things are useful for migrating to a
> future version of Squeak.
> 
> For the current project I provide a button for the customer which
> saves the image and quits so he can continue exactly where he left.
> This was not easy in other languages and I will see if people use it.
> 
> KF> 7. Eventually, I'll be done and I'll deploy the application.  Generally
> KF> I'll use some tool (Ant build files, Python setup files) to build the
> KF> release.  I'll generally test the deployed release in a "fresh" 
> KF> environment to duplication a potential user's experience.
> 
> As far as I know this is located somewhere between impossible and "you
> need a deep knowledge of the system". As well as getting previous but
> abandoned attempts to work again in a current image. No tool around to
> help with this.
> 
> I'd love to be corrected here but this is one of two big points which
> may still prevent me from making squeak the tool to earn my money
> with. The other one is printing. Well, the lack of it.
> 
> KF> discussions or documentation.  As I said, I've gotten hints about much
> KF> of the above but I'm trying to synthesis it into the whole "story".
> 
> Let's hope this leads to a story or recipe. AFAIK the only place where
> Squeak is "deployment ready" is Seaside.
> 
> Cheers
> 
> Herbert                            mailto:herbertkoenig at gmx.net
> 
> 
>