Christian I'm interested by the transformation code since last year we did a migration and made sure that we can migrate again the code of Mobydic an open-source simulation system. The logic of our approach is in store NGFileouter or something like that.
On Wed, Sep 13, 2017 at 7:58 AM, Christian Haider <christian.hai...@smalltalked-visuals.com> wrote: >> von Stephan Eggermont >> >> On 12-09-17 11:11, Denis Kudriashov wrote: >> > Maybe it is similar as porting GLORP into Pharo. Somebody can comment >> on this process. >> >> The important point is that the original code is in another dialect, and the >> idea >> is not to fork, as the original maintainer develops it further. >> That means that it is not a one-time translation, but is a set of >> transformation >> rules and platform specific packages that is applied every time something >> changes on either side. > > Stefan, you are good :-)! > > Exactly! The full code transformation from VW to GS is described as a value, > which gets interpreted by a generic code fileout machine. > A new version of the GS fileout can be generated at any time without human > intervention. > A SystemChange (the name of the value class) could be interpreted in > different ways. > > Currently, the transform is one way from VW to GS. > > I am very interested in changes people may do to the library, but for now, I > will keep the master in VW and integrate contributions by hand. > I am sure that, if the need arises, there will be a way to deal with a > two-way synchronization. But let's have a contribution first :-) > > Christian > >
