Hi. It looks like OSProcess (a dependency of Magma) is registering a class in the startUp list explicitly before ImageSegment (which was removed).� This was already fixed in new version of OSProcess.� Hence, ConfigurationOfMagma should be updated to use the new version of OSProcess.

Cheers

On Mon, Oct 24, 2011 at 4:54 PM, Ankur Sethi <get.me.ankur@gmail.com> wrote:
Hi,

I'm new to Pharo and Smalltalk in general. I'm trying to build a small
blogging application using Pharo and Seaside. I've decided to use
Magma for persistence, but I'm having some issues loading it in Pharo
1.3.

I loaded Magma the usual way:

Gofer new
� �squeaksource: 'MetacelloRepository';
� �package: 'ConfigurationOfMagma';
� �load.

(Smalltalk at:#ConfigurationOfMagma)
� �project latestVersion
� �load: 'Server';
� �load: 'Client'.

... and I was presented with a backtrace. Since didn't know how to get
a full backtrace out of Pharo in plain text, I took a screenshot:
http://imagebin.org/180559

I know this is not adequate, but I'm hoping someone can help me get
Pharo to give me information about this issue in a more convenient
format.

When I told Pharo to abandon loading the package and then re-evaluated this:

(Smalltalk at:#ConfigurationOfMagma)
� �project latestVersion
� �load: 'Server';
� �load: 'Client'.

... then everything went just fine. I even tried creating a Magma
repository, which worked. However, some things were totally borked in
my Pharo image. I couldn't get the System Browser to do syntax
highlighting, for one.

I'm using Pharo1.3 + CogVM 13307 on Mac OS X Lion.

I hope I made sense.

Thanks.

--
Ankur Sethi
(GeneralMaximus on IRC and elsewhere)




--
Mariano
http://marianopeck.wordpress.com