hdan@walt.cc.utexas.edu (Dan Higdon) (12/01/89)
Have any of you had the chance to use Digitalk's Smalltalk/V PM yet? I've been given the ol' "7-10 days" before I see mine, and was hoping to get some opinions/gotchas, etc. from someone already using it. 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? Thanks in advance for humoring an impatient curious person. hdan@sleepy.cc.utexas.edu (Really Dan Higdon)
cooper@netcom.UUCP (Ken Cooper) (12/02/89)
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 =============================================================================