Yanni,<div><br></div><div>Thanks!<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<a href="http://jenkins.lukas-renggli.ch/view/Seaside%203.0/" target="_blank">http://jenkins.lukas-renggli.<u></u>ch/view/Seaside%203.0/</a><br>
<br>
On that site is a Pier3/Margritte3/Seaside-3.1 build as well.<br></blockquote><div><br></div><div>Oh, maybe I will try that as a starting point. Thanks!</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
However, AFAICT, all the builds are based on Pharo-1.3, which may be an issue for you.</blockquote><div><br></div><div>I want to use Seaside, Magritte, Fuel (as a back-up storage facility, though primary right now), and Glorp via DBXTalk for relational DB I/O. That&#39;s my goal.�</div>
<div><br></div><div>Perhaps you are right and I am too early at adopting DBXTalk. It looks like it should simplify some of the DB storage.</div><div>�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 I build my image from Pharo-1.4, adding Seaside-3.0, Magritte2, Pier2.<br></blockquote><div><br></div><div>I do not need Pier per se. Rather, I simply had no images where the basic Magritte tutorials worked. None of them worked properly right out of the box. But you are saying that Magritte2 in Pharo-1.4, with Seaside 3.0 works together... ... ... so I will try it again.�</div>
<div><br></div><div>Do you need 1.4, and why? -- if you do not mind sharing.�</div><div>-</div><div><br></div><div>Let me say: because these configuration problems can be such a pain, especially when one is not aware of the nuances of various packages one might want to adopt, I only recently abandoned my Pharo-1.2 one-click derived image when I had troubles connecting to a DB. I figured it was time to do a complete upgrade. But it has turned into a nightmare, and my project has hit a standstill,�</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">((Smalltalk at: #ConfigurationOfFuel) project version: &#39;1.8&#39;)<br>

load.<br>
</blockquote>
<br>
I use version 1.7, but because I don&#39;t want the other packages in the image, I only load:<br>
<br>
FuelTests-MartinDias.157.mcz<br>
Fuel-MartinDias.479.mcz<br></blockquote><div><br></div><div>Thank you!�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I&#39;ve not tried the 1.8 version yet. If you&#39;re having trouble with Fuel, you might want to load and run the tests.<br></blockquote><div><br></div><div>In 1.4 Fuel worked &quot;out of the box&quot;, but in the Pier based image, it did not.�</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&gt; Thanks for any insight you can offer in advance.<br>
<br>
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....<br></blockquote><div>
<br></div><div>Pending your answers to my query about why you chose 1.4 over 1.3, I will start fresh again.�</div><div><br></div><div>Cheers &amp; Thanks,</div><div>Cam</div></div><br></div>