[Cuis-dev] Porting from Pharo

[Nicolas Cellier]

Has tonel really been conceived as an interchange format? I doubt it.
The meta-data lies somewhere else at best (git author) or nowhere at
worse as underlined by Boris
(the committer is not necessarily the author).

My understanding is that the chunks were considered horrible for
reading and reviewing code.
And the switch to git tools (more specifically github tools, code
review, merge requests, etc...) did expose the chunks too much.
Chunks were not designed for human consumption. Pharo (Gemstone) guys
wanted something looking more like native Smalltalk.

IMO, using tonel for dialect interchange is a poor choice.

Le sam. 1 mai 2021 à 22:22, Gerald Klix via Cuis-dev
<cuis-dev at lists.cuis.st> a écrit :
>
> Hi Philip,
>
> I have cloned the repo and will try it tomorrow.
>
>
> Thanks a bunch,
>
> Gerald
>
>
> On 2021-05-01 21:45, Philip Bernhart via Cuis-dev wrote:
> > Hi Gerald,
> >
> > I just pushed my not-yet-started port efforts:
> >
> > https://github.com/Phantasus/Cuis-Smalltalk-Tonel
> >
> > Maybe someone could use it as a starting point.
> >
> > What I did until now was to export the tonel code
> > into the directory and punched it into shape, so
> > that cuis can load it.
> >
> > It doesn't work. Also it seems that the authors of
> > the pharo image code were lost during the fileout.
> >
> > I haven't checked pharo8 for months, but is it known
> > to delete the code authors? Maybe because now that
> > information is held in iceberg/git?
> >
> >
> > Cheers,
> > Philip
> >
> >
> > Gerald Klix via Cuis-dev <cuis-dev at lists.cuis.st> writes:
> >
> >> Hi all,
> >>
> >> is there an easy way to port source code from
> >> Pharo to Cuis?
> >>
> >> I am aware of the tedious way:
> >>
> >> - File the package into a Pharo image
> >> - File out the Categories involved
> >> - Implement whatever it takes to
> >>     achieve compatibility.
> >>
> >>
> >> Thanks and Best Regards,
> >>
> >> Gerald
> >> --
> >> Cuis-dev mailing list
> >> Cuis-dev at lists.cuis.st
> >> https://lists.cuis.st/mailman/listinfo/cuis-dev
> >
> --
> Cuis-dev mailing list
> Cuis-dev at lists.cuis.st
> https://lists.cuis.st/mailman/listinfo/cuis-dev