Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!portc01.blue.aol.com!newsxfer2.itd.umich.edu!www.nntp.primenet.com!nntp.primenet.com!news.bbnplanet.com!cpk-news-hub1.bbnplanet.com!newsfeed.internetmci.com!news.webspan.net!ix.netcom.com!netcomsv!uu3news.netcom.com!netcomsv!uu4news.netcom.com!telesoft!east.alsys.com!news
From: Bob Manjoney <rjm@snet.net>
Subject: [VA] VisualAge 3.0 Professional/ENVY omission
Content-Type: text/plain; charset=us-ascii
Message-ID: <328C885C.73A7@snet.net>
Sender: news@thomsoft.com
Reply-To: rjm@snet.net
Content-Transfer-Encoding: 7bit
Organization: Thomson Software Products, Burlington, MA, USA
Mime-Version: 1.0
Date: Fri, 15 Nov 1996 15:12:28 GMT
X-Mailer: Mozilla 3.0 (Win95; I)
Lines: 24

Does anyone know why a seemingly useful feature was omitted from the
ENVY part of Visualage?  When running ENVY with VisualWorks a while
back, there was a concept known as "Application Configurations" - that
allowed you to denote, among other things, compatibility among editions
of a particular app.


  Where this was particularly useful was when you loaded an edition of
an application, ENVY would check that not only the correct prerequisites
for that app were present in your image, but that their editions were
*compatible* with the edition of the prerequisites present in the image
when the app being loaded was versioned...essentially this provides a
way of saying that an app needs not only a particular prerequisite, but
one that is compatible with a certain edition of that prerequisite, and
not necessarily a *specific* edition.  

Not having this feature leads to all sorts of problems where simply
having a particular prerequisite loaded is not a guarantee that the
application will load/run properly.

Why was this feature removed?  Is there another way to effect the same
behavior that I'm unaware of?

Bob Manjoney
