On 11/06/12 7:39 PM, Cameron Sanders wrote:
My Pier download was what was available on Saturday at http://www.piercms.com/download.
I thought you were referring to a build from: http://jenkins.lukas-renggli.ch/view/Seaside%203.0/ On that site is a Pier3/Margritte3/Seaside-3.1 build as well. However, AFAICT, all the builds are based on Pharo-1.3, which may be an issue for you. I build my image from Pharo-1.4, adding Seaside-3.0, Magritte2, Pier2.
Then as I noted in that post, I pulled in DBXTalk according to specs on http://dbxtalk.smallworks.com.ar/Download/.
I've used an earlier Glorp port, without problem, but don't use Glorp anymore. I've never used the latest DBXTalk. The Phoseydon scaffolding seems interesting, but you might want to ask the authors what their opinion is on its readiness (the last I remember, from a year or two ago, is was a first release). Note that Magritte3 was done earlier this year, so you may have some issues there.
*What version Magritte should I be using?*
The one that works for you :). Seriously though, Pier seems to be okay with either Magritte version, so whichever one Phoseydon needs will settle it - IIUC, Phoseydon uses Magritte, but I'm too lazy to check at the moment.
As an aside, in a 1.4 build, I pulled in Magritte3 via the following, and that fixed some name conflicts.
What name conflicts did you have? What tools had the conflicts? One of the key "fixes" of Magritte3 was to eliminate overloading of the #description method.
Is this the proper way to load it to work with seaside?
That's the way I would load it (but I'd leave off the Morphic stuff).
((Smalltalk at: #ConfigurationOfFuel) project version: '1.8') load.
I use version 1.7, but because I don't want the other packages in the image, I only load: FuelTests-MartinDias.157.mcz Fuel-MartinDias.479.mcz I've not tried the 1.8 version yet. If you're having trouble with Fuel, you might want to load and run the tests.
Thanks for any insight you can offer in advance.
Whenever I add a new framework, I start from my base image which has all the frameworks that I currently use. Then I load and run the tests for the new framework I want to use. If there are problems, I then start from a basic Pharo image (plus any pre-req packages for the new framework). You should not have to do this, unless you are using frameworks that are relatively new, or you're using a newer Pharo image.