Newbie-Accessible Squeak

Karl Wilson khwilson at bigfoot.com
Thu Mar 22 18:38:02 UTC 2001


>I'd like to be able to document/demonstrate the building of a software system
>sequentially, using live objects and text, and be able to show changes to the
>system over time.
>
>I don't think the current authoring/programming environment in Squeak
>supports that directly; there is the assumption that everything is already
>compiled in and ready to run.
>
>Or is there?
>
>Projects support isolation and reverting.
>
>Projects can be chained using the InternalThreadNavigationMorph.
>
>Projects can carry their own change sets along with them.
>
>So is it possible to have the first project of a presentation be isolated (so
>it can be reverted), and have other projects linked to it so that we see the
>incremental development of a software system?
>
>Would it be possible to navigate back to the prior project and see the system
>the way it was before loading the current project? (i.e could all the chained
>projects be isolated)?

The less elegant thing I was visualizing was:

say you want to see how the PDA was made - you file in a category of 
classes called PDARevisions which contains classes named - 
PDAMorphR1, PDAMorphR2, PDAMorphR3 - and be able to play with each 
one - go back and forth - compare, break, modify, branch off wildly 
at different stages in the design - then when you're done just dump 
the PDARevisions category

...but I'm sure something named InternalThreadNavigationMorph beats 
that idea hands down. ;?)

Karl





More information about the Squeak-dev mailing list