LSWVST Migrating from Visual Smalltalk

Migrating from VSE is much easier because LSWVST offers a compatibility to the binary Level of VSE:

Step 1: copy the LSWVST-Migration VM to your development application folder

In the example your VSE-Application is located under C:\MyVSEApp. Your Image File is MyVseImage.exe and the SLL's are located in the Application directory. Copy the VSE Migration-VM from the LSWVST's VM Folder to the application  folder.

Step 2: Prepare your image to recognize the new LSWVST Virtual-Machine

The LSWVST Migration-VM containes the Primitive 180 which failes in VSE.

Just add a method

Object>>isNewVM
<primitive: 180>
^false

Then you can change your Smalltalk code where it is necessary.

Step 3: Starting the VSE Image with the LSWVST Virtual-Machine

Start your Application with LSWVST.exe MyVseImage.exe.

Now your VSE-Legacy application should start with the LSWVST Virtual-Machine. Now it depends how far you want to go with the migration. It is recommended to switch your Development-Environment to LSWVST Team/S, migrate to the LSWVST's Library structure and migrate the GUI to LSWVST' s Orthogonality GUI. Also the Legacy PARTS applications should be migrated to LSWVST Prototypes.

A complete migration to LSWVST will give you all the advantages of a modern Smalltalk:

•  runs under Windows XP / Vista / CE/ Linux Ubuntu ( spring 2008 ); 32 and 64 Bit platforms
•  pure Unicode
•  an order of magnitude faster than Legacy VSE
•  can be compiled into one monolithic executable
•  can make use of native Threads