> On 18 Aug 2015, at 17:20, Pablo R. Digonzelli <pdigonze...@gmail.com> wrote: > > I can colaborate. I do not know if i have the time and technical skills to do > it alone, but for shure i can colaborate. > I think magma will be a very interesting option for object persistence in > pharo. > I am currently working with garage and glorp and i suffers the innecesary > complexity and other bad things thet persistence layer introduce in > developing pharo apps.
have you checked voyage? (to work with a MongoDB)… it will avoid all the pain of using a relational database. Esteban ps: But yes, I do believe having magma would be cool too. > > Pharo > > > Ing. Pablo Digonzelli > Software Solutions > IP-Solutiones SRL > Metrotec SRL > 25 de Mayo 521 > San Miguel de Tucumán > Email: pdigonze...@softsargentina.com > pdigonze...@gmail.com > Cel: 5493815982714 > > ----- Mensaje original ----- > De: "Torsten Bergmann" <asta...@gmx.de> > Para: "Any question about pharo is welcome" <pharo-users@lists.pharo.org> > CC: step...@stack.nl, steph...@free.fr, hila...@drgeo.eu, "Pablo Digonzelli" > <pdigonze...@gmail.com> > Enviados: Martes, 18 de Agosto 2015 10:26:44 > Asunto: Fwd: [ANN] Magma 1.5 > > Stephan Eggermont wrote: >> It is possible, and it needs someone who can deal with low-level >> details. Magma has its own mailing list. Chris has repeatedly said he'd >> be willing to help out, but is not willing to be the Pharo port maintainer. > > I asked Chris directly and you can find his answer here on the magma list: > > http://lists.squeakfoundation.org/pipermail/magma/2015-August/001955.html > > As ever it requires someone to move this forward to make it happen. > But as there was an initiative with Magma 1.3 for Pharo 1.3 already it does > not > seem impossible. > > Also - as Stef already pointed out - community services like CI could be used > to maintain it once an initial up to date port was done. > > Bye > T. >
