Hey Tim,
Would that be why so little "good" code has been written since 1972? ;-) Seriously though, I think a lot of people get so caught up in worrying about the trees that they have no idea what the forrest looks like.
Static maps printed out on paper are useful. Remember the original Smalltalk/V documentation? Very handy in it's day, and not totally useless 20 years later.
For Aaron:
Object browseHierarchy
is a reasonably good place to start. Less confusing than all this senseless category crap, IMO.
-Dean
Tim Rowledge tim@sumeru.stanford.edu Sent by: squeak-dev-bounces@lists.squeakfoundation.org 12/07/2004 01:16 AM Please respond to The general-purpose Squeak developers list
To: squeak-dev@lists.squeakfoundation.org cc: Subject: Re: Smalltalk class heirachy
"Aaron Gray" angray@beeb.net wrote:
Thats horrible, I meant a nice preferably UML notation chart that I
could
print out and put on my wall.
Not only is it unlikely to be convenient to print (got a 48" width carriage laserjet handy :-) ?) but it will almost certainly have changed by the time it finishes printing!
Dynamic tools are what you need old chap - paper and sourcecode files are the quaint relics of dinosaurian software fudging. We haven't done that stuff since, ooh, 1972 or so ... surely nobody does that stuff these days, not even those java chappies down the hall?
tim -- Tim Rowledge, tim@sumeru.stanford.edu, http://sumeru.stanford.edu/tim Disc space, the final frontier!