Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!gatech!swrinde!howland.reston.ans.net!vixen.cso.uiuc.edu!newsfeed.internetmci.com!news.dacom.co.kr!news.uoregon.edu!cs.uoregon.edu!reuter.cse.ogi.edu!qiclab.scn.rain.com!slc.com!servio!servio!aland
From: aland@servio.slc.com (Alan Darlington)
Subject: VA Window Builder  (was Re: Your oppionion about PARTS?)
Message-ID: <1996Feb26.214823.25927@slc.com>
Sender: news@slc.com (USENET News)
Nntp-Posting-Host: servio
Organization: GemStone Systems, Inc., Beaverton OR, USA
References: <4gamg9$kas@freeside.cls.de> <4gfba8$k39@watnews2.watson.ibm.com> <4ghhv7$les@news1.panix.com>
Date: Mon, 26 Feb 1996 21:48:23 GMT
Lines: 26

dsiegel@panix.com (David M. Siegel) writes:
> David N. Smith <dnsmith@watson.ibm.com> wrote:
> >Even if we presume that vissies (my just-made-up name for visual
> >thingies as in VA and PARTS) are a better way to initially build
> >a new vissie, there are other issues:
<snip> 
> VA, at least, has fair to good source code control support (a few
> ideosyncracies around the edges that IBM's been fixing from version to
> version). They can be filed out and distributed.  On my experience,
> it'll be another version or two before VA's integration into the
> Smalltalk environment is complete, though.
<snip>
Right.  My recent experience with distributing VA applications is that
the Envy mechanism (.dat files) works ok, but if you just file out the
code and file it into a new image, your application will not run.
You either need to bring up a window builder and re-save the run-
time code, or you need to send the message
#recalculatePartBuilderRecordFromArchivalCode to each application
class.  (I spent some time with IBM technical support on this one.
A few interesting non-source-code things are stored in the repository,
and these don't get re-created during file-in.)

  Cheers,
  Alan
    (standard disclaimer)

