Export source code from VisualAge to Squeak

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Export source code from VisualAge to Squeak

m.taborda
Hello.

Does anybody know if there is a tool to export source code from VisualAge to Squeak?

Thanks.

Maximiliano


Reply | Threaded
Open this post in threaded view
|

Re: Export source code from VisualAge to Squeak

Cees De Groot
VAST can file out in the standard chunked format. It's not entirely
Squeak compatible, so you either need to hack the text file or insert
some dummy code (IIRC mostly having to do with Applications) to
correspond with the incompatible chunks.

Of course, then there's the incompatibility in libraries... :-)

On 1/16/06, [hidden email] <[hidden email]> wrote:

> Hello.
>
> Does anybody know if there is a tool to export source code from VisualAge to Squeak?
>
> Thanks.
>
> Maximiliano
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Export source code from VisualAge to Squeak

Yanni Chiu
In reply to this post by m.taborda
[hidden email] wrote:
>
> Does anybody know if there is a tool to export source code from VisualAge to Squeak?

There's:
  SIF - http://www.pocketsmalltalk.com/sif/
  Rosetta - http://rosettast.sourceforge.net/
  fileout, edit and filein

Is it a one time transfer. Or, do you need
to move code back and forth?


Reply | Threaded
Open this post in threaded view
|

Re: Export source code from VisualAge to Squeak

m.taborda
In reply to this post by m.taborda
Yes, it is a one time transfer

----- Mensaje original -----
De: Yanni Chiu <[hidden email]>
Fecha: Lunes, Enero 16, 2006 3:34 pm
Asunto: Re: Export source code from VisualAge to Squeak

> [hidden email] wrote:
> >
> > Does anybody know if there is a tool to export source code from
> VisualAge to Squeak?
>
> There's:
>  SIF - http://www.pocketsmalltalk.com/sif/
>  Rosetta - http://rosettast.sourceforge.net/
>  fileout, edit and filein
>
> Is it a one time transfer. Or, do you need
> to move code back and forth?
>
>
>