Hi Thushar,

Magma's developer mostly uses Squeak, so the latest version of Pharo
that Magma works more or less out-of-the-box on is 1.3.
I made a start on porting it to 1.4, and then 2.0 but then promptly
ran out of time. �However, as far as I'm aware the porting should
mostly consist of the change to SystemAnnouncer, and Filesystem as you
mentioned.
Magma has a pretty comprehensive test suite, so it should be
relatively easy to verify any porting effort.

I know that people seem to be gravitating towards other solutions, as
St�phane mentioned, but Magma is still an excellent tool, and is
ridiculously simple to use. �I like it enough that for my own
projects, I'm still using Pharo 1.3 so I can use it, until the desire
to use 2.0 and beyond finally pushes me into completing my porting
effort ;)

If you do want to give the porting a go yourself, I'd suggest posting
to the Magma list. �Chris is very supportive of porting efforts.

Regards,
Stuart

On 4 June 2013 22:32, Thushar G R <thushar.gr@gmail.com> wrote:
> Hi all,
>
>
> I am new here in this list. I have already asked this question in stack
> overflow, but not much luck. So i thought ill contact the gurus directly.
>
> I am considering Magma to be used for one of my projects , which is nothing
> but a custom game center to connect my game and store user details and
> retrieve it. This would be the first time that i will be using pharo for one
> of my projects ( in fact this is the first time that i am able to decide for
> my self - the client has not preferences in terms of technology selection).
>
> So my concern is this, is Magama upgraded to be used in Pharo 2.0? What if i
> load it �and change the SystemChangeNotifiers with SystemAnnouncer and so on
> , will it cause any trouble in the future. I Appreciate any comments for
> this.
>
>
> Regards
>
> thushar