Github / Pharo / VisualWorks porting tools

MM
Martin McClure
Sat, Sep 21, 2019 12:06 AM

Hi Tom,

After a brief look at the code, I think that shared variables that are
defined in a class will become class variables. It looks like shared
variables defined directly in a namespace will log a warning and be
otherwise ignored.

This could obviously be improved; submissions are welcome.

Regards,
-Martin

On 9/19/19 2:07 PM, Tom Robinson wrote:

Martin,

Does SETT deal with shared variables? Shared variables directly in
namespaces? Or are these still something that needs doing?

Regards,

Tom

On 9/17/2019 9:07 AM, Martin McClure wrote:

If you need to extract code from a VW Store repository and get the
result in Tonel format, there's SETT (Store Export to Tonel Tools).

https://github.com/GemTalk/SETT

Regards,
-Martin

On 9/17/19 7:48 AM, Stéphane Ducasse wrote:

You should contact Pavel Krivanek because he did an excellent work
to port VW code to Pharo for Schmidt pro (without the need of VW).
Also Christian haider presented at ESUG last year a migration from
VW to Pharo.

Stef

On 17 Sep 2019, at 16:16, Sasa Prokic via Esug-list
<esug-list@lists.esug.org mailto:esug-list@lists.esug.org> wrote:

Hi Alexandre,

is there also a migrator for other way around?

Sasha

Sent from Yahoo Mail on Android
https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature

    On Tue., 17 Sep. 2019 at 9:00 a.m., Alexandre Bergel
    <abergel@dcc.uchile.cl mailto:abergel@dcc.uchile.cl> wrote:
    We have developed an automatic migrator from Pharo 2 VW. You can
    find it here:
    https://github.com/ObjectProfile/Pharo2VW

    Alexandre

    > On Sep 17, 2019, at 9:36 AM, Carsten Härle
    <Carsten.Haerle@straightec.de
    mailto:Carsten.Haerle@straightec.de> wrote:
    >
    > Hi,
    >
    > there is a lot of Smalltalk code in Github for Pharo and
    VisualWorks.
    > The main repository for Seaside seems to be Github also.
    >
    > Which VisualWorks tools are available to support code exchange
    with Github and Pharo?
    > How does the Cincom developer team do the porting of new
    versions, e.g. for Seaside?
    >
    > I found a Cypress interchange format implementation for
    VisualWorks from Travis Griggs:
    > https://github.com/CampSmalltalk/STIG
    >
    > However the code 7 years old and does not work in current
    VisualWorks  versions and has several bugs.
    > I started fixing it, but before I invest to much effort, I
    would  like to ask how other people do the porting from and to
    Github / Pharo or other dialects.
    >
    > Regards
    > Carsten
    > --
    > Carsten Härle,
    > straightec GmbH, Frankfurter Straße 48, 63150 Heusenstamm,
Germany
    > +49 6104  6008-0
    > https://www.straightec.de https://www.straightec.de/
    >
    > _______________________________________________
    > Esug-list mailing list
    > Esug-list@lists.esug.org mailto:Esug-list@lists.esug.org
    > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

    _______________________________________________
    Esug-list mailing list
    Esug-list@lists.esug.org mailto:Esug-list@lists.esug.org
http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org


Esug-list mailing list
Esug-list@lists.esug.org mailto:Esug-list@lists.esug.org
http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org


Stéphane Ducasse
http://stephane.ducasse.free.fr
http://www.synectique.eu / http://www.pharo.org
03 59 35 87 52
Assistant: Julie Jonas
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley,
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France


Esug-list mailing list
Esug-list@lists.esug.org
http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

Hi Tom, After a brief look at the code, I *think* that shared variables that are defined in a class will become class variables. It looks like shared variables defined directly in a namespace will log a warning and be otherwise ignored. This could obviously be improved; submissions are welcome. Regards, -Martin On 9/19/19 2:07 PM, Tom Robinson wrote: > Martin, > > Does SETT deal with shared variables? Shared variables directly in > namespaces? Or are these still something that needs doing? > > Regards, > > Tom > > On 9/17/2019 9:07 AM, Martin McClure wrote: >> If you need to extract code from a VW Store repository and get the >> result in Tonel format, there's SETT (Store Export to Tonel Tools). >> >> https://github.com/GemTalk/SETT >> >> Regards, >> -Martin >> >> On 9/17/19 7:48 AM, Stéphane Ducasse wrote: >>> You should contact Pavel Krivanek because he did an excellent work >>> to port VW code to Pharo for Schmidt pro (without the need of VW). >>> Also Christian haider presented at ESUG last year a migration from >>> VW to Pharo. >>> >>> Stef >>> >>>> On 17 Sep 2019, at 16:16, Sasa Prokic via Esug-list >>>> <esug-list@lists.esug.org <mailto:esug-list@lists.esug.org>> wrote: >>>> >>>> Hi Alexandre, >>>> >>>> is there also a migrator for other way around? >>>> >>>> Sasha >>>> >>>> Sent from Yahoo Mail on Android >>>> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature> >>>> >>>>     On Tue., 17 Sep. 2019 at 9:00 a.m., Alexandre Bergel >>>>     <abergel@dcc.uchile.cl <mailto:abergel@dcc.uchile.cl>> wrote: >>>>     We have developed an automatic migrator from Pharo 2 VW. You can >>>>     find it here: >>>>     https://github.com/ObjectProfile/Pharo2VW >>>> >>>>     Alexandre >>>> >>>>     > On Sep 17, 2019, at 9:36 AM, Carsten Härle >>>>     <Carsten.Haerle@straightec.de >>>>     <mailto:Carsten.Haerle@straightec.de>> wrote: >>>>     > >>>>     > Hi, >>>>     > >>>>     > there is a lot of Smalltalk code in Github for Pharo and >>>>     VisualWorks. >>>>     > The main repository for Seaside seems to be Github also. >>>>     > >>>>     > Which VisualWorks tools are available to support code exchange >>>>     with Github and Pharo? >>>>     > How does the Cincom developer team do the porting of new >>>>     versions, e.g. for Seaside? >>>>     > >>>>     > I found a Cypress interchange format implementation for >>>>     VisualWorks from Travis Griggs: >>>>     > https://github.com/CampSmalltalk/STIG >>>>     > >>>>     > However the code 7 years old and does not work in current >>>>     VisualWorks  versions and has several bugs. >>>>     > I started fixing it, but before I invest to much effort, I >>>>     would  like to ask how other people do the porting from and to >>>>     Github / Pharo or other dialects. >>>>     > >>>>     > Regards >>>>     > Carsten >>>>     > -- >>>>     > Carsten Härle, >>>>     > straightec GmbH, Frankfurter Straße 48, 63150 Heusenstamm, >>>> Germany >>>>     > +49 6104  6008-0 >>>>     > https://www.straightec.de <https://www.straightec.de/> >>>>     > >>>>     > _______________________________________________ >>>>     > Esug-list mailing list >>>>     > Esug-list@lists.esug.org <mailto:Esug-list@lists.esug.org> >>>>     > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >>>> >>>> >>>> >>>>     _______________________________________________ >>>>     Esug-list mailing list >>>>     Esug-list@lists.esug.org <mailto:Esug-list@lists.esug.org> >>>> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >>>> >>>> _______________________________________________ >>>> Esug-list mailing list >>>> Esug-list@lists.esug.org <mailto:Esug-list@lists.esug.org> >>>> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >>> >>> -------------------------------------------- >>> Stéphane Ducasse >>> http://stephane.ducasse.free.fr >>> http://www.synectique.eu / http://www.pharo.org >>> 03 59 35 87 52 >>> Assistant: Julie Jonas >>> FAX 03 59 57 78 50 >>> TEL 03 59 35 86 16 >>> S. Ducasse - Inria >>> 40, avenue Halley, >>> Parc Scientifique de la Haute Borne, Bât.A, Park Plaza >>> Villeneuve d'Ascq 59650 >>> France >>> >>> >>> _______________________________________________ >>> Esug-list mailing list >>> Esug-list@lists.esug.org >>> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >>> >> >> >> _______________________________________________ >> Esug-list mailing list >> Esug-list@lists.esug.org >> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > > > _______________________________________________ > Esug-list mailing list > Esug-list@lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org
SP
Sasa Prokic
Sat, Sep 21, 2019 4:03 AM

Hi Martin,
I thought of that path, its just small effort comoaring to benefits of extract automation. Will play with SETT and see how it goes. 
Thank you,Sasha

Sent from Yahoo Mail on Android

On Fri., 20 Sep. 2019 at 7:37 p.m., Martin McCluremartin.mcclure@gemtalksystems.com wrote:    Hi Sasha,
I don't think you can specify one package or bundle to extract. SETT will extract all publishes after a given date/time. If you want to just get a particular bundle, you could either 1) Publish just that bundle to Store, then use SETT to extract just that bundle, or 2) Extract one or more existing Store publishes that contain more than the one bundle you want, then delete the directories of Tonel files that are the code for unwanted packages.
SETT is not currently under active development (it is working well enough for our current needs) but enhancements to it are welcome.
Regards, -Martin

On 9/17/19 8:37 PM, Sasa Prokic wrote:

Hi Martin,
thank you for the info. Can one extract just selected package/boundle portion from store repository?
Regards, Sasha

Sent from Yahoo Mail on Android

On Tue., 17 Sep. 2019 at 11:07 a.m., Martin McClure martin.mcclure@gemtalksystems.com wrote:  If you need to extract code from a VW Store repository and get the
result in Tonel format, there's SETT (Store Export to Tonel Tools).

https://github.com/GemTalk/SETT

Regards,
-Martin

On 9/17/19 7:48 AM, Stéphane Ducasse wrote:

You should contact Pavel Krivanek because he did an excellent work to
port VW code to Pharo for Schmidt pro (without the need of VW).
Also Christian haider presented at ESUG last year a migration from VW to
Pharo.

Stef

On 17 Sep 2019, at 16:16, Sasa Prokic via Esug-list
<esug-list@lists.esug.org mailto:esug-list@lists.esug.org> wrote:

Hi Alexandre,

is there also a migrator for other way around?

Sasha

Sent from Yahoo Mail on Android
https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers⁡_wl=ym⁡_sub1=Internal⁡_sub2=Global_YGrowth⁡_sub3=EmailSignature

    On Tue., 17 Sep. 2019 at 9:00 a.m., Alexandre Bergel
    <abergel@dcc.uchile.cl mailto:abergel@dcc.uchile.cl> wrote:
    We have developed an automatic migrator from Pharo 2 VW. You can
    find it here:
    https://github.com/ObjectProfile/Pharo2VW

    Alexandre

    > On Sep 17, 2019, at 9:36 AM, Carsten Härle
    <Carsten.Haerle@straightec.de
    mailto:Carsten.Haerle@straightec.de> wrote:
    >
    > Hi,
    >
    > there is a lot of Smalltalk code in Github for Pharo and
    VisualWorks.
    > The main repository for Seaside seems to be Github also.
    >
    > Which VisualWorks tools are available to support code exchange
    with Github and Pharo?
    > How does the Cincom developer team do the porting of new
    versions, e.g. for Seaside?
    >
    > I found a Cypress interchange format implementation for
    VisualWorks from Travis Griggs:
    > https://github.com/CampSmalltalk/STIG
    >
    > However the code 7 years old and does not work in current
    VisualWorks  versions and has several bugs.
    > I started fixing it, but before I invest to much effort, I
    would  like to ask how other people do the porting from and to
    Github / Pharo or other dialects.
    >
    > Regards
    > Carsten
    > --
    > Carsten Härle,
    > straightec GmbH, Frankfurter Straße 48, 63150 Heusenstamm, Germany
    > +49 6104  6008-0
    > https://www.straightec.de https://www.straightec.de/
    >
    > _______________________________________________
    > Esug-list mailing list
    > Esug-list@lists.esug.org mailto:Esug-list@lists.esug.org
    > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

    _______________________________________________
    Esug-list mailing list
    Esug-list@lists.esug.org mailto:Esug-list@lists.esug.org
    http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org


Esug-list mailing list
Esug-list@lists.esug.org mailto:Esug-list@lists.esug.org
http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org


Stéphane Ducasse
http://stephane.ducasse.free.fr
http://www.synectique.eu / http://www.pharo.org
03 59 35 87 52
Assistant: Julie Jonas
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley,
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France


Esug-list mailing list
Esug-list@lists.esug.org
http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

Hi Martin, I thought of that path, its just small effort comoaring to benefits of extract automation. Will play with SETT and see how it goes.  Thank you,Sasha Sent from Yahoo Mail on Android On Fri., 20 Sep. 2019 at 7:37 p.m., Martin McClure<martin.mcclure@gemtalksystems.com> wrote: Hi Sasha, I don't think you can specify one package or bundle to extract. SETT will extract all publishes after a given date/time. If you want to just get a particular bundle, you could either 1) Publish just that bundle to Store, then use SETT to extract just that bundle, or 2) Extract one or more existing Store publishes that contain more than the one bundle you want, then delete the directories of Tonel files that are the code for unwanted packages. SETT is not currently under active development (it is working well enough for our current needs) but enhancements to it are welcome. Regards, -Martin On 9/17/19 8:37 PM, Sasa Prokic wrote: Hi Martin, thank you for the info. Can one extract just selected package/boundle portion from store repository? Regards, Sasha Sent from Yahoo Mail on Android On Tue., 17 Sep. 2019 at 11:07 a.m., Martin McClure <martin.mcclure@gemtalksystems.com> wrote: If you need to extract code from a VW Store repository and get the result in Tonel format, there's SETT (Store Export to Tonel Tools). https://github.com/GemTalk/SETT Regards, -Martin On 9/17/19 7:48 AM, Stéphane Ducasse wrote: > You should contact Pavel Krivanek because he did an excellent work to > port VW code to Pharo for Schmidt pro (without the need of VW). > Also Christian haider presented at ESUG last year a migration from VW to > Pharo. > > Stef > >> On 17 Sep 2019, at 16:16, Sasa Prokic via Esug-list >> <esug-list@lists.esug.org <mailto:esug-list@lists.esug.org>> wrote: >> >> Hi Alexandre, >> >> is there also a migrator for other way around? >> >> Sasha >> >> Sent from Yahoo Mail on Android >> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers⁡_wl=ym⁡_sub1=Internal⁡_sub2=Global_YGrowth⁡_sub3=EmailSignature> >> >>    On Tue., 17 Sep. 2019 at 9:00 a.m., Alexandre Bergel >>    <abergel@dcc.uchile.cl <mailto:abergel@dcc.uchile.cl>> wrote: >>    We have developed an automatic migrator from Pharo 2 VW. You can >>    find it here: >>    https://github.com/ObjectProfile/Pharo2VW >> >>    Alexandre >> >>    > On Sep 17, 2019, at 9:36 AM, Carsten Härle >>    <Carsten.Haerle@straightec.de >>    <mailto:Carsten.Haerle@straightec.de>> wrote: >>    > >>    > Hi, >>    > >>    > there is a lot of Smalltalk code in Github for Pharo and >>    VisualWorks. >>    > The main repository for Seaside seems to be Github also. >>    > >>    > Which VisualWorks tools are available to support code exchange >>    with Github and Pharo? >>    > How does the Cincom developer team do the porting of new >>    versions, e.g. for Seaside? >>    > >>    > I found a Cypress interchange format implementation for >>    VisualWorks from Travis Griggs: >>    > https://github.com/CampSmalltalk/STIG >>    > >>    > However the code 7 years old and does not work in current >>    VisualWorks  versions and has several bugs. >>    > I started fixing it, but before I invest to much effort, I >>    would  like to ask how other people do the porting from and to >>    Github / Pharo or other dialects. >>    > >>    > Regards >>    > Carsten >>    > -- >>    > Carsten Härle, >>    > straightec GmbH, Frankfurter Straße 48, 63150 Heusenstamm, Germany >>    > +49 6104  6008-0 >>    > https://www.straightec.de <https://www.straightec.de/> >>    > >>    > _______________________________________________ >>    > Esug-list mailing list >>    > Esug-list@lists.esug.org <mailto:Esug-list@lists.esug.org> >>    > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >> >> >> >>    _______________________________________________ >>    Esug-list mailing list >>    Esug-list@lists.esug.org <mailto:Esug-list@lists.esug.org> >>    http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >> >> _______________________________________________ >> Esug-list mailing list >> Esug-list@lists.esug.org <mailto:Esug-list@lists.esug.org> >> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > > -------------------------------------------- > Stéphane Ducasse > http://stephane.ducasse.free.fr > http://www.synectique.eu / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, Bât.A, Park Plaza > Villeneuve d'Ascq 59650 > France > > > _______________________________________________ > Esug-list mailing list > Esug-list@lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >