Magma June 2010

magma@lists.squeakfoundation.org

4 participants
6 discussions

[ANN] ConfigurationOfMagma for Magma 1.1r1
by Miguel Enrique Cobá Martínez 20 Jul '10

20 Jul '10

I'm pleased to announce that the ConfigurationOfMagma now includes support for loading version 1.1r1 of Magma. In a Pharo or PharoCore 1.0 image evaluate: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. To install the Magma Client evaluate: ConfigurationOfMagma project latestVersion load: 'Client' To install the Magma Server evaluate: ConfigurationOfMagma project latestVersion load: 'Server' To install the Magma Tester evaluate: ConfigurationOfMagma project latestVersion load: 'Tester' Then if you want, run the test suite. Evaluate in a workspace: MagmaTestCase allowWriteBarrier: false. MagmaTestCase fullSuite maDebug. Enjoy -- Miguel Cobá http://miguel.leugim.com.mx

2 4

Maui video?
by Chris Muller 14 Jun '10

14 Jun '10

> Or maybe I'll just load up the DB with my domain in a Squeak image where all > of these tools work :). I've watched a video of Maui in action and its > pretty cool! What video?!

2 1

materializing a MaCommitLogRecord
by Dave Woodward 14 Jun '10

14 Jun '10

I'm wondering if it is possible to directly materialize the objects in a MaCommitLogRecord instance. It seems that the commit log records are used exclusively for "advancing" the repository. However I'm wondering if I can use the commit log as a sort of poor-man's audit log and if I'd be able to manually extract objects from specific commit log records. Right now when I try to materialize a record in Pharo 1.0, I get an error because the serializer tries to call basicNew: on the MagmaLocalLocation class. I'm not sure if this is even a good path to take, so fell free to tell me I'm crazy or that I shouldn't go there :) I'm also wondering if the commits could be "rolled back" so as to be able to rewind the database back to a specific commit? I see how one can restore up to a certain point in time, but I'm just wondering if there is any more specific way to "un-apply" the commit records. -- Dave Woodward

2 5

Re: [Pharo-project] Magma in Pharo 1.1
by Chris Muller 13 Jun '10

13 Jun '10

The next release of Magma will have all of the underscore assignments removed. Until then, you may invoke the preference that allows underscore assignment. 2010/6/13 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Sorry, I forgot the screenshot > > On Sun, Jun 13, 2010 at 9:52 PM, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: >> >> Hi. I was trying the welcome workspace of Pharo 1.1 in order to install >> Magma but it fails. I am evaluating: >> >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfMagma'; >> load. >> >> ((Smalltalk at: #ConfigurationOfMagma) project latestVersion) load >> >> >> The error was a Sintax Error in >> >> lazyX >> ^ x ifNil: [x _ Period or right bracket expected ->42] >> >> >> I attach screenshot. It seems the problem with the underscore as they are >> not allowed anymore as asiggment in Pharo 1.1. In order to appear in Pharo >> welcome workpsace this should be working. >> >> If someone makes the changes and updates de configuration please let me >> know (sorry but I don't have time to do it myself). Otherwise, I will have >> to remove it from Pharo 1.1 workspace as it doesn't work and makes >> confusion. >> >> Thanks >> >> Mariano >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

1 0

Magma in Pharo 1.1
by Mariano Martinez Peck 13 Jun '10

13 Jun '10

Hi. I was trying the welcome workspace of Pharo 1.1 in order to install Magma but it fails. I am evaluating: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. ((Smalltalk at: #ConfigurationOfMagma) project latestVersion) load The error was a Sintax Error in lazyX ^ x ifNil: [x _ Period or right bracket expected ->42] I attach screenshot. It seems the problem with the underscore as they are not allowed anymore as asiggment in Pharo 1.1. In order to appear in Pharo welcome workpsace this should be working. If someone makes the changes and updates de configuration please let me know (sorry but I don't have time to do it myself). Otherwise, I will have to remove it from Pharo 1.1 workspace as it doesn't work and makes confusion. Thanks Mariano

1 0

Ma Armored Code version wrong MCM for 1.1r1
by Miguel Enrique Cobá Martínez 07 Jun '10

07 Jun '10

Hi Chris, I found that the package version for Ma Armored Code specified in the MCM for 1.1r1 (http://squeaksource.com/Magma/1.1r1.mcm) is 146, but the version specified in the magma wiki page (http://wiki.squeak.org/squeak/2657) is 147. I assume that the correct one is 147. If that is correct, then you need to generate a new mcm for 1.1r1. Cheers -- Miguel Cobá http://miguel.leugim.com.mx

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma June 2010