Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!gatech!newsfeed.internetmci.com!in2.uu.net!news.new-york.net!ritz.mordor.com!jpletzke
From: jpletzke@ritz.mordor.com (Jonathan Pletzke)
Subject: Re: Team/V vs. ENVY/Developer
X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
Lines: 32
Organization: Mordor International
Message-ID: <DLnBA2.JLK@ritz.mordor.com>
References: <4e2lv3$sc8@news.fonorola.net>
Date: Tue, 23 Jan 1996 17:58:49 GMT

Robert MacLean (maclean@simware.com) wrote:
: My company currently purchased VisualSmalltalk 3.1 (without the Team/V 
: source management component).  Now we are looking at source management 
: solutions for the VisualSmalltalk environment.
: 
: One solution is to upgrade VisualSmalltalk 3.1 to VisualSmalltalk 
: Enterprise 3.1 and use the Team/V source management component integrated 
: into the Enterprise edition.

Both options assist in the area of source code management.  ENVY requires 
a more rigorous approach, whereas Team/V will let you do just about 
anything.  If you are also managing other source code outside Smalltalk 
in Sync with the ST code (i.e. using PVCS to manage C source code), then 
you may wish to have an integrated tool for managing both types of code 
(which includes buying the PVCS for Windows or OS/2 for your C/C++ 
code).  Team/V does not provide manual or automatic dependecy notation, 
where ENVY does support dependencies (pre-requisites).  ENVY also 
supports assignment of a manager to each module, where with Team/V you've 
got to manage it on paper.  Team/V supports storage of any type of 
object, but not all can be controlled in groups.  I dont know if ENVY 
supports binary objects.

Team V is only available for the Digitalk Smalltalk, but ENVY is 
available for VisualWorks, Digitalk, and IBM, (not to mention embedded ST 
applications).

I find ENVY preferable for the way I think and work.

-Jonathan Pletzke
President
The Technical Expertise Corporation

