Hi Wolfgang,

I share your view on doIt's, simply because they survive fileOut's and  
fileIn's better and are kept in the context where they belong to.

What do you do with doIt's like "Smalltalk garbageCollect", e.g. those  
which are not related to project work?

/Klaus

On Fri, 28 Jul 2006 10:54:06 +0200, Wolfgang Eder <edw at generalmagic.at>  
wrote:

> stéphane ducasse wrote:
> [lots of stuff snipped]
> I would like to make a point that Doits should not be
> a separate concept:
> I am aware that it is common practice to have Doit
> methods in workspaces, for example.
> For a long time now, I and my colleages have stored all
> the Doits as methods in a Script class made for this purpose.
>
> The rationale is that Doits are part of the code,
> and should be treated the same by the CM system (Envy in our case).
>
> This works out very well. I especially like the fact that
> refactorings reliably catch the Doits as well, since they are
> normal methods.
>
> I cannot see any disatvantages from this approach, and it keeps
> things really simple, imho.
>
> Thanks,
> Wolfgang
>
>