I've added https://code.google.com/p/xtreams/issues/detail?id=2, so
interested people please reply there.

Thanks!

On 18 April 2013 18:35, Nicolas Cellier
<nicolas.cellier.aka.nice at gmail.com> wrote:
> Hi Martin,
> I recently ported some of the VW fixes to Squeak, but with a fully manual
> mode:
> - open a VW image and track the diffs
> - try to understand the motivation of changes, the implementation and
> analyze which change apply or not (no UninterpretedBytes in Squeak for
> example, ...)
> - update VW image
> - copy/paste the code in Squeak, manually correct a XT prefix here and there
>
> Since not all features can be ported (differences in sockets/pipes etc...)
> this process is fragile and somehow open to randomness, but that's what you
> can get from a human ;)
>
> Ideally, we should proceed with test driven updates, first update/merge the
> tests, then the implementation, but since a test can span several packages,
> that's not always easy to deal with and following the history of commits is
> not that easy in VW...
> Maybe a well structured feature branch/bugfix branch policy coupled with bug
> reports and using git support might indeed help sifting.
> Anyway, I'm still a few months back in change history, so that leave some
> place for experimentation
>
>
> 2013/4/18 <mkobetic at gmail.com>
>
>> As Jan mentioned, in https://github.com/mkobetic/Xtreams I'm primarily
>> just experimenting with Cypress. However the master branch there is
>> misleading, it contains a very early port of Xtreams to ST/X (there's a much
>> more up to date version in Jan's ST/X project @
>> https://swing.fit.cvut.cz/jenkins/job/xtreams_reports/).
>>
>> However if you look at some of the other branches in the github project
>> you can find a fairly up to date, Cypress formatted dump from VW as well as
>> the results of Sean's ESUG effort to add namespace-prefix mapping to
>> Filetree (branch pharo_experiment). My ultimate goal is to test Dale's idea
>> to maintain a cross-dialect project as parallel branches in git. However we
>> still need to iron out various dialect differences in terms of what they
>> emit as Cypress formatted output. BTW, does anyone know if git/github can
>> handle absence of a master branch? I'd be inclined to just delete the master
>> from the repository if that works well.
>>
>> I've been planning to ping Sean about his Filetree fixes for a while, but
>> I need to find the time to be able to actually act on it :-). The
>> prefix-namespace mapping is crucial to make the parallel branch approach at
>> all feasible. There's also the Environment effort on Squeak side which may
>> obviate the prefix mapping need, but it seems to be still in fairly early
>> stages.
>>
>> So far it was mostly Nicolas' manual effort that brought VW updates over
>> the Squeak/Pharo side. I think it was a while since the last time he's done
>> that, so the VW port is probably ahead somewhat. But Xtreams development
>> isn't that active anymore. Most of our Xtreams related efforts are about
>> using them for various things, so any changes are mostly fixes or small
>> improvements driven by that use. So in some sense a manual update could be a
>> feasible approach at this point. But I would really like to turn the project
>> into a more collaborative effort, where updates can flow reasonably in any
>> direction.
>>
>> While I'm on the topic, I'm considering some API changes and am not sure
>> how to go about discussing it. I don't want to cross post discussions to a
>> number of mailing lists, so I think I'm inclined to just cross-post an
>> invitation to anyone interested to subscribe to the Issues on the project
>> site (https://code.google.com/p/xtreams/) and have those discussions there.
>> Any thoughts on that?
>>
>> "Frank Shearar"<frank.shearar at gmail.com> wrote:
>> > How up to date is https://github.com/mkobetic/Xtreams/ ? That's surely
>> > not the "canonical" repository, which would be in the Cincom Smalltalk
>> > Public Repository. I think? Anyway, assuming it's up to date, one
>> > promising approach to using Martin Kobetic's repository directly is:
>> > * have a way of importing chunk format stuff from a GitHub repository
>> > (see Squeak's inbox for my
>> > doesn't-support-filetree-yet-but-can-do-chunk-format InstallerGitHub
>> > (and I plan to submit a Gofer patch to do the same))
>> > * load into an Environment (Squeak 4.5 can do this, modulo its alpha
>> > state).
>> >
>> > It might even be possible to import into an Environment with the
>> > prefix-adding import and then fileout/monticelloise the resulting
>> > things as a prefix-using, non-Environments-requiring blob ready for
>> > everyone to use.
>> >
>> > frank
>> >
>>
>>
>
>
>
>