I have no idea how complicated this can be. I'm a bit reluctant to dive into this if we are only 2-3 people to use Glorp in Pharo.

Guillermo, Mariano, what was the process when you imported Glorp in the first place? How did you keep up with Glorp latest changes (From what I see in Store, development is not too active)?


On Fri, Sep 5, 2014 at 11:30 AM, Stephan Eggermont <stephan@stack.nl> wrote:
Sven wrote:
>Porting something cross platform is a huge amount of work, I think most of it was basically done by hand.
>This creates a huge maintenance problem of course. The same is true for Xtreams.
>Seaside seems to be able to manage this problem by being extremely careful.

We now have the infrastructure in place (CI) that supports a much better approach.
We could use a vw image to download the current version from the public store
and generate the platform-independent mczs from there. That of course requires
changes to the VW code base to create and use platform classes. That is similar to
what we did in the other direction with Parasol, what Roassal does and Seaside.
If we make the (namespace) transformations explicit, we should be able to sync
in two directions.

Stephan