Pretty cool.
Made me think of graphs, so I found and ported a strong connected
components analysis algorithm, hoping it would show where we can cut the
image. No such luck, it just shows that half the classes are cyclicly
connected...

Do you have this in reasonable changeset form, I can load it into images
that've been partially stripped?

Daniel

Henrik Gedenryd <h.gedenryd at open.ac.uk> wrote:
> > This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> 
> --Boundary_(ID_3DikOC3YaKyMCj7do57BtQ)
> Content-type: text/plain; charset=US-ASCII
> Content-transfer-encoding: 7BIT
> 
> I made a sketchy Connectors hack a few weeks ago that gives you boxes and
> arrows representing modules and dependecies. You then try to rearrange them
> so that dependents are above ther dependees, if you succeed then all the
> arrows are pointing downwards and their color goes green, which indicates
> "good" deps, bad ones are automatically colored red. Sounds like a game
> doesn't it?
> 
> Kinda fun in itself, almost, but it gets bad when you try it with eToy for
> example. I've made some flaps that are the results of trying out various
> parts of the image. The gif shows the dependencies from eToy to Morphic--and
> back, in red. Pity the one who takes on that task. Which is a shame since it
> is probably the most important one of all.
> 
> <http://lucs.lu.se/People/Henrik.Gedenryd/Squeak/ModuleDependencies.zip>
> 
> Warning: it's an 11M+ zipped image since projects aren't module-aware yet.
> 
> Henrik
> 
>