Magma November 2011

magma@lists.squeakfoundation.org

2 participants
2 discussions

Re: [Pharo-users] [pharo-users] Can't Load Magma in Pharo 1.3
by Mariano Martinez Peck 05 Dec '11

05 Dec '11

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(a)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

2 7

Traits and Magma in Pharo 1.3
by Panu Suominen 02 Nov '11

02 Nov '11

Hi, I have a little problem using Magma, Pharo 1.3 & co. Magma seems to load fine to empty 1.3 image. Tests does not seem to work but data can be stored and loaded. However after loading more code to the image debuger pops up saying that Trait does not understand typeOfClass. This is raised from MaClassDefinition >> initializeForm:. This problem makes impossible to load a trait to the image. Method naming suggest that traits should not end up there anyways? I hacked my self around this problem by adding a guarding line in the begining of MaClassIdManage>>refreshInImageDefinition:. It goes like this: aClass isTrait ifTrue:[^self]. It enables me to load codes to the image, but I have no idea about the possible side effects of this change. Maybe someone more knowledgeable should investigate the issue? :) -- Panu

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma November 2011