IMHO, the CVST project is probably the best long term idea.  I would also 
like to get Store open sourced, but the wheels of Cincom move slowly in 
that regard


At 07:22 PM 7/29/2002 -0500, Mark A. Schwenk wrote:

>On Mon, 2002-07-29 at 17:02, Sven C. Koehler wrote:
> > Hello all!
> >
> > What is the best practice when I want to write one source code
> > for both Squeak3 and VW5i.4.  By that I mean only the source code,
> > ignoring differences in supplied classes by the system.
> >
> > I also want to keep source code in a CVS repository, for easy
> > distribution (hence it suffices, if I can occasionally generate the
> > source code that is to be checked in into the CVS repository).
> >
> > All I tried so far turned out not to work (using Pepe2, fileout ..
> > filein).  Thus, I believe that I need to maintain two different
>versions
> > of the source code; one for Squeak, and one for VW...
> >
> > Any better ideas?
> >
> > Best regards,
> >
> > Sven C. Koehler
>
>I made this same inquiry a couple of years ago (okay, it wasn't vw5i.4,
>per se, but perhaps vw5i).
>
>Since then, I have moved code back and forth using a couple of different
>strategies.
>
>Speaking from memory here, it seemed if you loaded the VW3 compatibility
>parcel and filed things out in Chunk format from VisualWorks, you could
>read it into Squeak without much difficulty.
>
>Going from Squeak to VisualWorks was where I ran into problems. I ended
>up creating a parcel of code for VisualWorks that would allow the Squeak
>Chunk format to be read in. I went further than that and started on a
>Squeak compatibility parcel that made my porting efforts easier, adding
>many of the Classes and methods I missed from Squeak and even curly
>brace support into VisualWorks.
>
>I also worked a bit on the CVST project. When I was working with it we
>used Eric Arseneau's SIF code for the interchange format.
>
>I haven't used Göran Hultgren's CVS client for Squeak, so I can't
>comment on its current status.
>
>Perhaps some of the CampSmalltalk folks can share their recent
>experience with moving between Squeak and VisualWorks, so I've copied
>this message to that list. I'll post a final summary of any ensuing
>discussion of this to both lists and to the VisualWorks and Squeak
>wikis.
>
>-Mark Schwenk
>  WellThot Inc.
>
>On Mon, 2002-07-29 at 17:02, Sven C. Koehler wrote:
> > Hello all!
> >
> > What is the best practice when I want to write one source code
> > for both Squeak3 and VW5i.4.  By that I mean only the source code,
> > ignoring differences in supplied classes by the system.
> >
> > I also want to keep source code in a CVS repository, for easy
> > distribution (hence it suffices, if I can occasionally generate the
> > source code that is to be checked in into the CVS repository).
> >
> > All I tried so far turned out not to work (using Pepe2, fileout ..
> > filein).  Thus, I believe that I need to maintain two different versions
> > of the source code; one for Squeak, and one for VW...
> >
> > Any better ideas?
> >
> > Best regards,
> >
> > Sven C. Koehler

<Talk Small and Carry a Big Class Library>
James Robertson
Product Manager, Cincom Smalltalk
jarober at gosmalltalk.com