I am forwarding this dialog I held with Stuart for reference in the list.
---------- Forwarded message ---------- From: Ramiro Diaz Trepat ramiro@diaztrepat.name Date: Sat, Jul 25, 2009 at 7:31 PM Subject: Re: Pharo To: Stuart Herring st-lists@stuartherring.com
Hi Stuart,That was a great idea, I did not know you could just drag & drop .sar files to the image. In spite of that, the server is not working in Pharo. When I run:
serverConsole := MagmaServerConsole new open: dbPath; processOn: 51001.
It hangs on MagmaSession>>submit:to:
It may have to do with the new Closures in Pharo, I don't know.
Cheers, and thanks for your help.
r.
On Sat, Jul 25, 2009 at 1:41 PM, Stuart Herring st-lists@stuartherring.comwrote:
On Sat, Jul 25, 2009 at 7:37 AM, Ramiro Diaz Trepat ramiro@diaztrepat.name wrote:
Is Magma currently installable on Pharo?
I have just successfully loaded r42Gamma5 into both Pharo, and Pharo-core-10388 - you have to click proceed twice for warnings about extensions to classes that no longer exist in Pharo, but otherwise it seems fine. I haven't actually tested using it yet though.
It looks like Chris didn't publish the .mcm for Gamma5, but if you download the .sar from Squeak Map and drag and drop it in to a running Pharo image, it installs fine.
It doesn't load in to 10392 though - installation aborts with Error: Key Not Found when it attempts to load Ma object serialization. That looks like a Pharo bug though, as attempts to debug it also give the same error.
Regards, Stuart
Also, I have tried only to use pharo as a client to connect to a Magma server, I thought this could work, but I get the following error: MessageNotUnderstood: BlockClosure>>maOn:do:on:do:
Again, Magma must extend BlockClosures, and that extension must not be happening in Pharo after installing the Magma .sar.
Cheers.
r.
On Sat, Jul 25, 2009 at 7:31 PM, Ramiro Diaz Trepat ramiro@diaztrepat.namewrote:
I am forwarding this dialog I held with Stuart for reference in the list.
---------- Forwarded message ---------- From: Ramiro Diaz Trepat ramiro@diaztrepat.name Date: Sat, Jul 25, 2009 at 7:31 PM Subject: Re: Pharo To: Stuart Herring st-lists@stuartherring.com
Hi Stuart,That was a great idea, I did not know you could just drag & drop .sar files to the image. In spite of that, the server is not working in Pharo. When I run:
serverConsole := MagmaServerConsole new open: dbPath; processOn: 51001.
It hangs on MagmaSession>>submit:to:
It may have to do with the new Closures in Pharo, I don't know.
Cheers, and thanks for your help.
r.
On Sat, Jul 25, 2009 at 1:41 PM, Stuart Herring < st-lists@stuartherring.com> wrote:
On Sat, Jul 25, 2009 at 7:37 AM, Ramiro Diaz Trepat ramiro@diaztrepat.name wrote:
Is Magma currently installable on Pharo?
I have just successfully loaded r42Gamma5 into both Pharo, and Pharo-core-10388 - you have to click proceed twice for warnings about extensions to classes that no longer exist in Pharo, but otherwise it seems fine. I haven't actually tested using it yet though.
It looks like Chris didn't publish the .mcm for Gamma5, but if you download the .sar from Squeak Map and drag and drop it in to a running Pharo image, it installs fine.
It doesn't load in to 10392 though - installation aborts with Error: Key Not Found when it attempts to load Ma object serialization. That looks like a Pharo bug though, as attempts to debug it also give the same error.
Regards, Stuart
On Sat, Jul 25, 2009 at 5:37 PM, Ramiro Diaz Trepat ramiro@diaztrepat.namewrote:
Also, I have tried only to use pharo as a client to connect to a Magma server, I thought this could work, but I get the following error: MessageNotUnderstood: BlockClosure>>maOn:do:on:do:
Again, Magma must extend BlockClosures, and that extension must not be happening in Pharo after installing the Magma .sar.
Hi! Perpahs I will say non sense things, but I will give it a shoot.
I have a similar problem when trying to use Glorp in Pharo. Glorp has extends methods in BlockContext. If you go to BlockContext you will see a category called *Glorp with a couple of methods.
Perhaps in these case, you have the same problem. What I did for Glorp, and it worked perfect, is to copy all the Magma methods in BlockContext (they should have 1 or more categorry called *Magma or something like that) to BlockClosure. In addition, I created a separate package called GlorpPharoPort with all the things to make Glorp work in Pharo. One of these things was these methods extensions to BlockClosure. Be aware this package should be loaded after the other packages.
I hope this helps.
Best,
Mariano
Cheers.
r.
On Sat, Jul 25, 2009 at 7:31 PM, Ramiro Diaz Trepat < ramiro@diaztrepat.name> wrote:
I am forwarding this dialog I held with Stuart for reference in the list.
---------- Forwarded message ---------- From: Ramiro Diaz Trepat ramiro@diaztrepat.name Date: Sat, Jul 25, 2009 at 7:31 PM Subject: Re: Pharo To: Stuart Herring st-lists@stuartherring.com
Hi Stuart,That was a great idea, I did not know you could just drag & drop .sar files to the image. In spite of that, the server is not working in Pharo. When I run:
serverConsole := MagmaServerConsole new open: dbPath; processOn: 51001.
It hangs on MagmaSession>>submit:to:
It may have to do with the new Closures in Pharo, I don't know.
Cheers, and thanks for your help.
r.
On Sat, Jul 25, 2009 at 1:41 PM, Stuart Herring < st-lists@stuartherring.com> wrote:
On Sat, Jul 25, 2009 at 7:37 AM, Ramiro Diaz Trepat ramiro@diaztrepat.name wrote:
Is Magma currently installable on Pharo?
I have just successfully loaded r42Gamma5 into both Pharo, and Pharo-core-10388 - you have to click proceed twice for warnings about extensions to classes that no longer exist in Pharo, but otherwise it seems fine. I haven't actually tested using it yet though.
It looks like Chris didn't publish the .mcm for Gamma5, but if you download the .sar from Squeak Map and drag and drop it in to a running Pharo image, it installs fine.
It doesn't load in to 10392 though - installation aborts with Error: Key Not Found when it attempts to load Ma object serialization. That looks like a Pharo bug though, as attempts to debug it also give the same error.
Regards, Stuart
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
On Thu, Jul 30, 2009 at 9:01 AM, Mariano Martinez Peckmarianopeck@gmail.com wrote:
Perhaps in these case, you have the same problem. What I did for Glorp, and it worked perfect, is to copy all the Magma methods in BlockContext (they should have 1 or more categorry called *Magma or something like that) to BlockClosure. In addition, I created a separate package called GlorpPharoPort with all the things to make Glorp work in Pharo. One of these things was these methods extensions to BlockClosure. Be aware this package should be loaded after the other packages.
Yes, ended up doing exactly this to get Magma working - I was going to post what I did, but I wanted to run the tests first, and changes in some of the Socket code means that the tests also need porting, and I ran out of time.
Regards, Stuart
On Wed, Jul 29, 2009 at 8:45 PM, Stuart Herring st-lists@stuartherring.comwrote:
On Thu, Jul 30, 2009 at 9:01 AM, Mariano Martinez Peckmarianopeck@gmail.com wrote:
Perhaps in these case, you have the same problem. What I did for Glorp,
and
it worked perfect, is to copy all the Magma methods in BlockContext (they should have 1 or more categorry called *Magma or something like that) to BlockClosure. In addition, I created a separate package called GlorpPharoPort with all
the
things to make Glorp work in Pharo. One of these things was these methods extensions to BlockClosure. Be aware this package should be loaded after the other packages.
Yes, ended up doing exactly this to get Magma working - I was going to post what I did, but I wanted to run the tests first, and changes in
Nice ;)
Now I am thinking most packages that extends BlockContext will have such problem :( However, be aware that (I think) Squeak is also trying to integrate closures (not only pharo).
some of the Socket code means that the tests also need porting, and I ran out of time.
What changes? IPv6?
Regards, Stuart _______________________________________________ Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
This sounds great guys.Stuart, are you interested in producing some Magma-Pharo package with me? If you are already advanced but still need some help let me know. Cheers.
r.
On Thu, Jul 30, 2009 at 12:52 AM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
On Wed, Jul 29, 2009 at 8:45 PM, Stuart Herring < st-lists@stuartherring.com> wrote:
On Thu, Jul 30, 2009 at 9:01 AM, Mariano Martinez Peckmarianopeck@gmail.com wrote:
Perhaps in these case, you have the same problem. What I did for Glorp,
and
it worked perfect, is to copy all the Magma methods in BlockContext
(they
should have 1 or more categorry called *Magma or something like that) to BlockClosure. In addition, I created a separate package called GlorpPharoPort with all
the
things to make Glorp work in Pharo. One of these things was these
methods
extensions to BlockClosure. Be aware this package should be loaded after the other packages.
Yes, ended up doing exactly this to get Magma working - I was going to post what I did, but I wanted to run the tests first, and changes in
Nice ;)
Now I am thinking most packages that extends BlockContext will have such problem :( However, be aware that (I think) Squeak is also trying to integrate closures (not only pharo).
some of the Socket code means that the tests also need porting, and I ran out of time.
What changes? IPv6?
Regards, Stuart _______________________________________________ Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
magma@lists.squeakfoundation.org
-
Mariano Martinez Peck -
Ramiro Diaz Trepat -
Stuart Herring