Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!ames!apple!netcom!cooper
From: cooper@netcom.UUCP (Ken Cooper)
Newsgroups: comp.lang.smalltalk
Subject: Re: Smalltalk/V PM
Message-ID: <4804@netcom.UUCP>
Date: 2 Dec 89 06:37:33 GMT
References: <21700@ut-emx.UUCP>
Reply-To: cooper@netcom.UUCP (Ken Cooper)
Distribution: comp.lang.smalltalk
Organization: NetCom- The Bay Area's Public Access Unix System {408 997-9175 guest}
Lines: 28

In article <21700@ut-emx.UUCP> hdan@walt.cc.utexas.edu (Dan Higdon) writes:
>
>For instance, how does it support Stand Alone Executables?  Is their
>a DLL involved, or does Stand Alone really mean Stand Alone?
>How does the image file fit into the scheme of things?
>

To quote the manual:

"The Smalltalk/V PM system includes two main pieces.  The DLL (Dynamic Link
Library) files are a collection of the shared, unchanging objects in the 
release system.  V.EXE is an executable snapshot of the current state of the
Smalltalk/V PM environment, a kind of group photo preserving the state of the
changable objects in the base system, and any new objects you create. 
Together, V.EXE and the .DLL files comprise what we refer to as the 'image.'"

We haven't used it much, but it looks like they've done some good things
with the MVC hierarchy and graphics (obviously motivated by the use of the
PM GUI API).  Unfortunately though, these changes are significant enough to
make porting applications unpleasant. It's probably time to consider getting
some more memory as well...

Ken

=============================================================================
Ken Cooper                                         USENET: cooper@netcom.uucp
Acumen Software                                Compu$erve: 71571,407
=============================================================================