>
> Treat me like a beginner. I have two targets:
>
> 1. I want to document the source code of Scratch.
>
> 2. I want to modify Scratch.
>
>
...
> You change code using browsers in Smalltalk itself.  It's not a good idea
> to
> try to change code in the files.
....

> You create new classes using a Smalltalk browser.  While you could use a
> file and file in the file it's not a good idea to change code in files.
>
>
>
> Squeak by Example [8] talks about a 'hierarchy browser' which is easy to
> find with the files provided with it. Is there a similar kind of thing to
> explore Scratch objects? If yes, how to get to it. If no, how do can I
> trace
> the hierarchy of inheritance objects used to make Scratch.


Yes, you can 'get behind the scenes in Scratch' by using a 'rabbit
hole' as Markus Gaelli wrote

http://lists.squeakfoundation.org/pipermail/squeak-dev/2013-January/168424.html

"You know that you can "shift click" into the top half of the R of
SCRATCH on the top left of Scratch -- then open the rabbit hole via
"turn fill screen off"...


The thread in January 2013 started by Stephane Rollandin asking
http://lists.squeakfoundation.org/pipermail/squeak-dev/2013-January/168401.html

<citation>
Hello,

I'm currently studying the Scratch code. The image I have (the BYOB 1.3
image) has a Smalltalk version of 'MIT Squeak 0.9.4 (June 1, 2003)'.

How could I find the original corresponding base Squeak image (that is,
the same image without Scratch code) ?

Stef
</citation>

HTH

--Hannes