Magma February 2011

magma@lists.squeakfoundation.org

11 participants
7 discussions

[ANN] New installation procedures for Magma
by Chris Muller 21 Feb '11

21 Feb '11

I am pleased to announce new packaging and configuration for the upcoming Magma 1.2 release, as well as future releases. About MaBase ------------------ Magma requires several prerequisite packages. These are now all kept in a SqueakSource project called "MaBase". This is the base-layer for all projects from Muller Automation, such as Magma, Maui, Ma client server, Banyan, and others, and includes packages up-to and including "Ma object serialization". SqueakSource ----------------- The source code for Magma is still hosted on SqueakSource under the "Magma" project. Thanks to new load-scripts, I no longer need to duplicate the base-layer packages in this squeaksource project. Good-bye, MagmaTester ----------------------------- "MagmaTester" has nothing to do with the the Magma test cases; it was just a sort of "Inbox" where Magma contributors could place their submissions. But there hasn't been a lot of activity from others in that project so, unless there is objection, I intend to delete the project. Load-scripts ------------ Installing Magma is now similar to other projects, by using a load-script. These load-scripts are documented in SqueakMap, and allow the same one-click loading convenience that has always existed (or, at least, intended!) for Magma. These scripts are more robust than what I have been using, because they allow loading of specific configuration of packages known to work together, as well as the latest code. And, when loading the latest code, (a.k.a., the "head" release), it does so in a fashion just like the Squeak trunk update mechanism; it merges into the image without overwriting any local changes, allowing collaboration to occur. For more details, please see: http://wiki.squeak.org/squeak/2657 Please let me know if you have any questions.

4 4

Can't connect to local machine
by Jeff Gray 18 Feb '11

18 Feb '11

Hi all, Magma newbie... In the help docs, to connect locally it says: myMagmaSession := MagmaSession openLocal: 'c:\myMagmaFolder\myRepository.magma'. As an experiment if I select: MagmaSession openLocal: 'c:\myMagmaFolder\myRepository.magma'. and print it, I get an error 'Could not open _open in use?' The directory is there but with no myRepsitory.magma file. If I create the file and try again Pharo freezes and I have to kill the task in the Windows Task Manager. What am I doing wrong? Pharo 1.1.1 Not sure which version of Magma I have. -- View this message in context: http://forum.world.st/Can-t-connect-to-local-machine-tp3312050p3312050.html Sent from the Magma mailing list archive at Nabble.com.

3 2

Strange ZeroDivide exception happened
by Denis Kudriashov 16 Feb '11

16 Feb '11

Hello. I have trouble with updating object in magma db on some computer. I have local repository magma usage. Environment is my client computer which I dont have access. When programme try to update state of some object I have exception ZeroDivide: MagmaSession>>signalExceptionLike: [] in [] in [] in MagmaSession>>submit:to: [] in [] in BlockClosure>>maOn:do:on:do: BlockClosure>>on:do: [] in BlockClosure>>maOn:do:on:do: BlockClosure>>on:do: BlockClosure>>maOn:do:on:do: [] in [] in MagmaSession>>submit:to: MagmaPreferences class>>showWhile: [] in MagmaSession>>submit:to: When programme update state of another class object all work good. Maybe somebody have this situation? Can it be related to some problems with disk? (bad sector). My programme work good on another computers. It is first bad case.

2 2

Magma repository on Squeaksource incomplete?
by Stuart Herring 16 Feb '11

16 Feb '11

Am I missing something, or have half the packages disappeared from http://www.squeaksource.com/Magma? Attempting to load 1.1r2 into a new image (via Metacello) and it fails pretty much immediately when it can't find Ma exception handling. Looking at the "latest" page in Squeaksource only shows: Magma Tools-cmm.52.mcz Magma client-cmm.534.mcz Magma seaside-cmm.5.mcz Magma server-cmm.421.mcz Magma tester-cmm.373.mcz MagmaTesterLoader-cmm.36.mcz WriteBarrier-cmm.28.mcz Which doesn't look right... Regards, Stuart

2 1

How to load Magma into Pharo 1.2?
by Marco A. Gonzalez 09 Feb '11

09 Feb '11

Hi, What is the currently recommended way to load Magma into Pharo 1.2? (Still learning in an attempt to move from Java and relational databases to Smalltalk) What I tried from a fresh install of Pharo 1.2RC2 from * instructions in the "Installing external projects" window displayed by evaluating "DEVImageWorkspaces openExternalProjectWorkspace" from the "Welcome to Pharo" window leads to a dependency problem with FlapTab. (I saw some posts relating to this that indicate that Miguel Coba knows about this) * instructions from Miguel Coba at http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg31841.ht… (September posting) lead to the following error: The method SmalltalkImage osVersion has been deprecated. Use OSPlatform * instructions from Miguel Coba but replacing MetaRepoForPharo11 with MetaRepoForPharo12 leads to the following error: The method SmalltalkImage osVersion has been deprecated. Use OSPlatform * instructions "Installing Magma" found on http://wiki.squeak.org/squeak/2657 (I used 1.1r1, 1.2alpha1 following the "you should see "r42Final" or a later version") lead to the following error: This package depends on the following classes: FlapTab - Marco A. ------------------------------------------------------ Marco A. Gonzalez email: marcoinc(a)mac.com

3 4

Shutdown
by Facundo Vozzi 08 Feb '11

08 Feb '11

Hi all, I'm testing my app on a production scenary where I would have a UPS conected to the server running magma. If I have a electrical power failure then the UPS send a signal to the server for shutdown it and in that moment I would like close all magma conections securely and shutdown magma server. The correct way to do that is send #cleanUp to the MagmaSession class ? Then I would need shutdown squeak by command line but I will read how to do that. Thanks in advance, FV

2 1

Trying to understand forwarding proxies
by Norbert Hartl 03 Feb '11

03 Feb '11

After 4 years of abstinence from Magma I try to get back in touch to evaluate some new ideas. I was thinking how to utilize magma in a cloud environment like the one from amazon. So I'm interested in possible scaling scenarios. If I understand it correctly then - magma uses a directory to write its files. That could be called the repository - one repository is served by one server at any time - a special mode is possible where the client and the server reside in the same image (thus having only the need for a single image) - HA splits one node over certain locations. A node is an arbitrary amount of servers serving a single shared repository - forwarding proxies can be made from server to server. So these are cross-domain/cross-repository Talking to magma is done using a session. So I can do the following. - talk to a HA node that will read from an arbitrary server but will commit to a single one - mimicking a domain model by using forwarding proxies. So objects partitioned over multiple repositories appear to be in the same domain - using multiple sessions to read from multiple servers. That would be the case of domain model partitioning Up to here I would like to know what is the tradeoff in using forwarding proxies. Is the whole communication done via the proxy on the first machine or is another session created to which the client has direct access? Or to be more precise: If I would have a forwarding proxy to a collection in another repository that would hold objects from a third repository and I would detect: an object from that collection to which server am I talking when invoking a method on that detected object? As far as I remember sessions are not the most performant thing to establish. Do I remember that correct and has this changed? Same question goes for the start of a repository. Is this a quick operation or are there a lot of preparation steps that make startup rather slow? I hope these are not too much dumb questions. I'm just thinking about possibilities to what would be worth to try out. With amazon you can have multiple machines attached to a shared block storage. That can share all the repositories over an arbitrary amount of machines. But at the moment I can see how to get a lot of benefit from that particular feature regarding magma. If forwarding proxies are not too expensive that would be still enable some things. thanks in advance, Norbert

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma February 2011