Magma September 2010

magma@lists.squeakfoundation.org

3 participants
5 discussions

[ANN] ConfigurationOfMagma for Pharo 1.0, Pharo 1.1 and Pharo 1.2
by Miguel Enrique Cobá Martínez 08 Dec '10

08 Dec '10

Hi all, a new version of ConfigurationOfMagma is available for Pharo. Notes: Pharo 1.0 ---------------------- - 1.1r1 is the last versions that works in Pharo 1.0. This is because upstream Magma code depends on code that only exists on Pharo 1.1 and superior. - Pharo 1.0 uses Preferences to enable/disable the underscore as assigment in code. This release captures current value of this preference. Enables it for loading Magma and restores it to the original value after installing Magma. Pharo 1.1, Pharo 1.2 ---------------------- - The configuration for these Pharo releases is based on the one from Pharo 1.0. - 1.1r2 uses a new baseline because Magma has a new package dependency (Ma files additions). - Pharo 1.1 and superior uses Scanner allowUnderscoreAsAssignment instead of Preferences. The current value is captured and restored after installation of Magma. - Pharo 1.1 and superior doesn't include FlapTab class anymore. Magma adds some methods to it so the Configuration adds an empty class named FlapTab before installing and removes from the system after installing. This avoid a warning prompt when installing Magma. - This Configuration includes support for installing Magma releases previous to 1.1r2. Those versions should install correctly on Pharo 1.1 and greater but if a lot of problems are detected, the support for those old versions will be removed, and only 1.1r2 and newer versions will be supported. Now that Pharo has Universes, Magma has different ConfigurationOfMagma in each universe for Pharo. Each of those Configuration install the appropriate packages in Pharo. Installing Magma Pharo 1.0 --------------- Evaluate: Gofer new squeaksource: 'UniverseForPharo10'; package: 'ConfigurationOfMagma'; load. And then, one of: ConfigurationOfMagma project latestVersion load: 'Client'. ConfigurationOfMagma project latestVersion load: 'Server'. ConfigurationOfMagma project latestVersion load: 'Tester'. latestVersion is 1.1r1 Pharo 1.1 --------------- Evaluate: Gofer new squeaksource: 'UniverseForPharo11'; package: 'ConfigurationOfMagma'; load. And then, one of: ConfigurationOfMagma project latestVersion load: 'Client'. ConfigurationOfMagma project latestVersion load: 'Server'. ConfigurationOfMagma project latestVersion load: 'Tester'. latestVersion is 1.1r2 Pharo 1.2 --------------- Evaluate: Gofer new squeaksource: 'UniverseForPharo12'; package: 'ConfigurationOfMagma'; load. And then, one of: ConfigurationOfMagma project latestVersion load: 'Client'. ConfigurationOfMagma project latestVersion load: 'Server'. ConfigurationOfMagma project latestVersion load: 'Tester'. latestVersion is 1.1r2 Comments and bugs accepted. Enjoy. -- Miguel Cobá http://miguel.leugim.com.mx

4 4

possible bug
by Elliot Finley 01 Oct '10

01 Oct '10

Hello, I just started playing with Magma, so it may be just me not knowing how to use it. I have a server running in image A on my machine. In image B on the same machine I have the following in a workspace: mySession := (MagmaRemoteLocation host: '10.215.90.59' port: 51001) newSession. mySession connectAs: 'elliot'. myRoot := mySession root. If I use '127.0.0.1' or 'localhost' as the host, then I get a timeout error when calling mySession>>connectAs: It says 'ConnectionTimedOut: Cannot connect to 10.215.90.74:51001' (10.215.90.74 is an address that I've had at one time). If I specifically use '10.215.90.59' as the host, then connectAs: works as normal, but then the following statement 'myRoot := mySession root.' fails with the 'ConnectionTimedOut: Cannot connect to 10.215.90.74:51001' error. Has anyone seen this before? What am I doing wrong? Thanks in advance, Elliot

2 2

possible bug
by Elliot Finley 28 Sep '10

28 Sep '10

I forgot to mention my machine and version of Magma. Macbook Pro (Max OS X 10.6) Pharo-1.1-11411dev10.07.1 Magma 11r2 Thanks, Elliot

1 0

magma collections - indexing and searching.
by Timothy James Ziebart 18 Sep '10

18 Sep '10

Hi all, I have setup a MagmaCollection with two indexes. I loaded the initial data and it appeared to be successful. I have the following search: getMessagesFor: aModule fieldName: aFieldName "Retreive message from the database" |aReader| aReader := (self root at: #fields) where:[ :each | (each fieldName at: aFieldName ) & (each moduleName at: aModule)]. ^aReader asArray. For the records loaded initially this works fine. However any records I add in the application do not get retrieved using the above method. But I can recover the new records searching on the fieldName and moduleName separately. So the indexes appear to be correct. Any Suggestions? Am I missing a step? Below I've included more details on the initial setup. Thanks again for your help. Tim Initial Setup: myCollection := MagmaCollection new. newIndex := MaSearchStringIndex attribute: #fieldName. myCollection addIndex: newIndex. newIndex := MaSearchStringIndex attribute: #moduleName. myCollection addIndex: newIndex. I added my records using a do loop: (fields ) do:[ :each | myCollection add: each ]. The resulting collection was written to Magma. LBCRepository commit:[LBCRepository root at: #fields put: myCollection ]. The addField method in the application is as follows: LBCRepository class method>> addField: aField self commit:[(self root at: #fields) add: aField]

2 1

Loading latest client and server.
by Timothy James Ziebart 05 Sep '10

05 Sep '10

I managed to install the magma server on a pharo 1.1 image including the OBMagmaBrowser. It appears to work fine. I can browse the repository. In a second image I loaded the client. When I run session := (MagmaRemoteLocation host: 'server' port: 51969) newSession. It appears to work properly give me an instance of a Magma Session. But when I go to connectAs: 'user' on the session I get the following message: MagmaReadServerTooFarBehind: MaSaveAndExitImageRequest cannot have variable sized instances Any Ideas? I tried using MagmaSession host: port: and I get the same result. Thank you. Tim

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma September 2010