Re: Try to load Pier2 into Pharo1.4

Damir, 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. Now I have a stable image, and I won't change a thing for a year... or until I hear that 2.0 is stable. 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. Good Luck! -Cam On Fri, Oct 5, 2012 at 2:11 AM, Damir Majer <damir(a)majcon.de> wrote: