John,

> As a programmer -- I agree.  Give me the darn browser over any printed
> documentation where I can perform a dynamic analysis and editing.  But
> as a designer, I can often make subjective and objective evaluations
> and draw conclusions of a class hierarchy more quickly by seeing it in
> UML or the like.  You know, funny things like duplication can jump out
> at you when seeing a UML, where they remain hidden in a code
> browser.

  I see your point, but just curious... What kind if "duplication" you
are referring to?  Is it something you could "calculate" by evaluating
one or two lines of Squeak code on the classes?

> Lastly, I work in a regulated environment that has been unwilling to
> do away with old paper relics.  So while I've been pushing it off, I
> will eventually have to develop a class diagram for documentation
> purposes of how we use Smalltalk in our regulated systems (ugh! -- do
> you sense my hesitancy).

  Oh, no.

-- Yoshiki