I'm soooo glad that Bob mentioned this first.  :-)

Having worked with VSE for years and with VA for the past 9 months or so, I
heartily agree that VA's use of ENVY is just too, too, too cumbersome.  I
much prefer the approach that was taken by those excellent Digitalkers with
their Team tools.

I hope that a Squeak source control mechanism can be implemented in such a
way that is more or less invisible to regular Smalltalkers.  Change
management is essential, but it shouldn't hinder us.  ENVY hinders me.

Cheers,

---==> Chris

PS>  I don't mean to imply that everything about VA is cumbersome.  Some of
the tools that are added by VA Assist Pro make the environment downright
friendly.  I just have a personal problem with the whole "ownership" concept
and how it was implemented in ENVY and at my company.

-----Original Message-----
From: Bob Arning [mailto:arning at charm.net]
Sent: Friday, August 17, 2001 4:36 PM
Subject: Re: [Modules] Images vs. module safety


On Fri, 17 Aug 2001 12:52:38 -0700 Allen Wirfs-Brock
<Allen_Wirfs-Brock at Instantiations.com> wrote:
>Nobody wants a Smalltalk system where it was hard to create or 
>change code? If somebody built it, nobody would use it.

How, then, can we explain ENVY?

Cheers,
Bob