Porting Squeak packages to VisualWorks


Squeak packages are managed with Monticello and are normally
available through SqueakMap (see http://seaside.st)

In most cases, VisualWorks ports are created from packages that
are not yet published on SqueakMap. Those Squeak packages are
taken from other sources (http://squeaksource.com/Seaside) and
are placed in subdirectory "Packages".

They all have the .mcz extension.

Seaside		Seaside2.7b1-mb.23.mcz
SeasideTesting	SeasideTesting-R1.4-mb.12.mcz
Mewa			Mewa.Seaside2.5-al.24.mcz

Packages need to be exported from Squeak using so-called "exporters".
The exporter framework is available as a Squeak package, also supplied
in subdirectory "Packages".

Exporters	PackageInfo-Exporters-mb.25.mcz

This Squeak package is actually an extension to PackageInfo-Base and
PackageInfo-Extras that are normally already in a Squeak image.

Exporters are supplied in subdirectory "Package Info" and must be
filed-in into Squeak.

Seaside		SeasideVWInfo.st
Chronology		ChronologyVWInfo.st
Mewa			MewaVWInfo.st

There is no SeasideTestingVWInfo.st file because the exporter for 
SeasideTesting is included inside the SeasideTesting package.

Once all the packages and corresponding exporters are loaded into
Squeak. Here is the Smalltalk code that must be executed in a Squeak
workspace.


For Chronology

	ChronologyVWInfo fileOutVW5.

For Seaside

	SeasideVWInfo fileOutVW5.

For SeasideTesting

	SeasideTestingVWInfo fileOutVW5.

For Mewa

	MewaVWInfo fileOutVW5.

The above generate Smalltalk source code files that can be file-in into
VisualWorks. These source code files are also included in subdirectory
"Exported".

Chronology		ChronologyVW5.st

Seaside		SeasideVW5.st

SeasideTesting	SeasideTestingVW5.st

Mewa			MewaVW5.st
