FYI. Is it interesting for pharo comunity migrate magma from squeak to pharo?.
Anyone knows if it is possible to do? Ing. Pablo Digonzelli Software Solutions IP-Solutiones SRL Metrotec SRL 25 de Mayo 521 San Miguel de Tucumán Email: [hidden email] [hidden email] Cel: 5493815982714 ----- Mensaje reenviado ----- De: "Chris Muller" <[hidden email]> Para: "magma" <[hidden email]> Enviados: Jueves, 13 de Agosto 2015 12:42:16 Asunto: Fwd: [ANN] Magma 1.5 I am pleased to announce version 1.5 of Magma for Squeak 5, now available on SqueakMap. Magma allows multiple Squeak images to collaborate on a single, large object model, with the robustness and control expected from a database. It offers the most transparent db access possible for Smalltalk, affording the user the ability to develop complex, performant designs, iteratively, on-the-fly. It has been designed for "continuous flow" development, the way Smalltalkers like and expect to work. For example, I could have connections open to 3 separate databases, open transactions in any of them, and having restructured a class hierarchy in the model, and stepping through the debugger when that "final boarding call" for my flight is announced. Thanks to the image, this scenario has never been a problem for Smalltalkers and Magma is deliberate to ensure this flow is maintained. Once at 10K feet, I can resume stepping through that same debugger within 5 seconds of restarting the image, DB connections intact, commit my transactions when I'm ready, done. Magma handles every aspect of that use-case correctly even in multi-user environments, and has so many safety and integrity features, it is the safest way to develop and keep a model in Squeak. This release coincides with the release of Squeak 5, and has many improvements and fixes over Magma 1.4. Detailed notes about these improvements are available at http://wiki.squeak.org/squeak/6209. - Chris _______________________________________________ Magma mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/magma |
Magma is a very valuable tools!
I have no idea of the complexity to deal with that. For example we have trait in Pharo, I guess it have implication. Hilaire Le 14/08/2015 00:15, Pablo R. Digonzelli a écrit : > FYI. Is it interesting for pharo comunity migrate magma from squeak to pharo?. > Anyone knows if it is possible to do? > > > > Ing. Pablo Digonzelli > Software Solutions > IP-Solutiones SRL > Metrotec SRL > 25 de Mayo 521 > San Miguel de Tucumán > Email: [hidden email] > [hidden email] > Cel: 5493815982714 > > ----- Mensaje reenviado ----- > De: "Chris Muller" <[hidden email]> > Para: "magma" <[hidden email]> > Enviados: Jueves, 13 de Agosto 2015 12:42:16 > Asunto: Fwd: [ANN] Magma 1.5 > > I am pleased to announce version 1.5 of Magma for Squeak 5, now > available on SqueakMap. Magma allows multiple Squeak images to > collaborate on a single, large object model, with the robustness and > control expected from a database. It offers the most transparent db > access possible for Smalltalk, affording the user the ability to > develop complex, performant designs, iteratively, on-the-fly. > > It has been designed for "continuous flow" development, the way > Smalltalkers like and expect to work. For example, I could have > connections open to 3 separate databases, open transactions in any of > them, and having restructured a class hierarchy in the model, and > stepping through the debugger when that "final boarding call" for my > flight is announced. > > Thanks to the image, this scenario has never been a problem for > Smalltalkers and Magma is deliberate to ensure this flow is > maintained. Once at 10K feet, I can resume stepping through that same > debugger within 5 seconds of restarting the image, DB connections > intact, commit my transactions when I'm ready, done. Magma handles > every aspect of that use-case correctly even in multi-user > environments, and has so many safety and integrity features, it is the > safest way to develop and keep a model in Squeak. > > This release coincides with the release of Squeak 5, and has many > improvements and fixes over Magma 1.4. Detailed notes about these > improvements are available at http://wiki.squeak.org/squeak/6209. > > - Chris -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu |
In reply to this post by pdigonzelli1
Hi pablo
I always considered Magma as a good idea/system. Now Chris always thought that Pharo was not good for him because we were supported by Gemstone. I never really understood. So a port could be good but if Chris is not interested it may be difficult. Now may be you should contact him and see. We will pay attention and we can offer CI support and other. I should say that I do not understand why people do not understand that we are not doing Pharo for the fame, for us, (I would be much much smarter to work in Javascript) but to support that they can do business and be successful. Especially since Pharo is open and that we pay attention to other code and point of view. I was and I'm still puzzled but I stopped to think about it and I'm just continuing to push the idea to build an eco system where you guys can make a living out of this great system. (I created a company and I would love to create a couple of others so Pharo as a platform is key for me and I'm also concerned with that. Stef Le 13/8/15 18:15, Pablo R. Digonzelli a écrit : > FYI. Is it interesting for pharo comunity migrate magma from squeak to pharo?. > Anyone knows if it is possible to do? > > > > Ing. Pablo Digonzelli > Software Solutions > IP-Solutiones SRL > Metrotec SRL > 25 de Mayo 521 > San Miguel de Tucumán > Email: [hidden email] > [hidden email] > Cel: 5493815982714 > > ----- Mensaje reenviado ----- > De: "Chris Muller" <[hidden email]> > Para: "magma" <[hidden email]> > Enviados: Jueves, 13 de Agosto 2015 12:42:16 > Asunto: Fwd: [ANN] Magma 1.5 > > I am pleased to announce version 1.5 of Magma for Squeak 5, now > available on SqueakMap. Magma allows multiple Squeak images to > collaborate on a single, large object model, with the robustness and > control expected from a database. It offers the most transparent db > access possible for Smalltalk, affording the user the ability to > develop complex, performant designs, iteratively, on-the-fly. > > It has been designed for "continuous flow" development, the way > Smalltalkers like and expect to work. For example, I could have > connections open to 3 separate databases, open transactions in any of > them, and having restructured a class hierarchy in the model, and > stepping through the debugger when that "final boarding call" for my > flight is announced. > > Thanks to the image, this scenario has never been a problem for > Smalltalkers and Magma is deliberate to ensure this flow is > maintained. Once at 10K feet, I can resume stepping through that same > debugger within 5 seconds of restarting the image, DB connections > intact, commit my transactions when I'm ready, done. Magma handles > every aspect of that use-case correctly even in multi-user > environments, and has so many safety and integrity features, it is the > safest way to develop and keep a model in Squeak. > > This release coincides with the release of Squeak 5, and has many > improvements and fixes over Magma 1.4. Detailed notes about these > improvements are available at http://wiki.squeak.org/squeak/6209. > > - Chris > _______________________________________________ > Magma mailing list > [hidden email] > http://lists.squeakfoundation.org/mailman/listinfo/magma > > |
In reply to this post by pdigonzelli1
On 13/08/15 18:15, Pablo R. Digonzelli wrote:
> FYI. Is it interesting for pharo comunity migrate magma from squeak to pharo?. > Anyone knows if it is possible to do? 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. Stephan |
Free forum by Nabble | Edit this page |