CVST is supposed to be a perfect fit for this. Note that the goal with CVST is not just occasional code exchange between dialects, but it is aimed at actual team development using CVS in a cross-dialect environment. It is still quite far from perfect, but I think it can already do a decent job. At CS4 in Colorado we've made a great progress, Bryan Hogan has built a VisualAge port and Steve Waring and Jerry Bell have built a Dolphin port. And we have tuned the SIF toolkit to produce the exact same SIF output from VA, Dol and VW, which is quite important if you want to avoid tons of little false differences in the CVS repository. This was all released as version 0.7 and is available from http://cvstproj.sf.net. Unfortunately we didn't have any avid Squeaker in our group so the Squeak port is still at version 0.6 and needs to catch up (any takers ?). Also, so far the only port with GUI tools is VW, so I would recommend to start looking at that one. And if you have any questions just ask in the cvstproj-devel mailing list (cc-ed above).

Martin

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