On Fri, Oct 5, 2012 at 4:50 PM, Cameron Sanders <camsanders(a)aol.com> wrote:
I would help if I could, but I don't know enough to answer your question.
Hence the private answer.
What I know is this: early in the summer, when I was trying to upgrade
from Pharo 1.2 to a modern version of Pharo, and gain simple DB
connectivity (via glorp), I had a difficult time getting the few packages I
needed to all play well together. My needs were simple: Pier for the
seaside and magritte, and glorp, and Fuel. I found that I could only work
with a very lean image to avoid conflicts: raw-release + pier3 + glorp +
opendbx + fuel.
I know that feeling, that's why I suggest everybody to have their own
I explain that in
Now I have a stable image, and I won't change a thing for a
until I hear that 2.0 is stable.
Cameron, if you finally go to production with your app, let us know so that
we can add you to:
Pharo 2.0 looks like it has a nice set of tools!
Magritte3 moved the xxxDescription methods to the instance side, and it
uses pragmas, so the name matters less. (Not at all? i don't recall.)
Overall, it was an improvement in the name space and so I am glad I spent
the couple of days learning the new tools and converting/upgrading.
You might be hitting the same namespace problems that I hit related to
Magritte3. The problem is #description ... -- i forget the details.
Nick Ager was quite helpful pointing to a video showing how to upgrade
from Magritte2 to 3.
yes, and he gave a presentation at ESUG 2012 and at PharoConf. But I think
there are no videos :(
On Fri, Oct 5, 2012 at 2:11 AM, Damir Majer <damir(a)majcon.de> wrote:
Hi Cam, hi Mariano,
> thanks for your replies.
> As I understand, it seem´s that Pier2 is not stable (ready?) for the new
> Pharo1.4 because of the OmniBrowser Dependencies.
> So I guess, that I have to use Pier3 with the latest Pharo1.4/2.0 to get
> stable version of Pier?
Magritte, Pier and Related Tools ...