Metacello configuration of Magma

[Miguel Enrique Cobá Martinez]

I have published the Metacello configuration of Magma in the
MetacelloRepository of squeaksource.com.

Take a PharoCore 10506 and evaluate in a workspace:

Gofer it
  squeaksource: 'MetacelloRepository';
  package: 'ConfigurationOfMagma';
  load.

Then load the default group that loads the Magma Client:

((Smalltalk at: #ConfigurationOfMagma) project version: '1.0r43') load

this is equivalent to:

((Smalltalk at: #ConfigurationOfMagma) project version: '1.0r43') load:
'Client'.

To load the Magma Server evaluate:

((Smalltalk at: #ConfigurationOfMagma) project version: '1.0r43') load:
'Server'.

And to load the Magma Tester evaluate:

((Smalltalk at: #ConfigurationOfMagma) project version: '1.0r43') load:
'Tester'.

This last one will load also OSProcess that is used by the Magma Tester
to do the stress testing of Magma.

Notes:
- WriteBarrier is a package loaded by Magma. This requires NewCompiler
as dependency but as NewCompiler is being rewritten currently, isn't
loaded as a dependency. 
- Magma makes use of ProjectHistory that doesn't exist anymore in Pharo.
Magma will fix this by conditionally testing for ProjectHistory by means
of Smalltalk at: #ProjectHistory.
- This is the first configuration for Magma and will be modified in
response to the feedback you give me.
- Currently the blessing is #development. Maybe this should be marked as
#stable in order to load with:
((Smalltalk at: #ConfigurationOfMagma) project latestVersion) load.
This way it will install the latest non-development version available in
MetacelloRepository without having to specify a version number.
- This configuration executes a preLoadDoIt with the following code:

Smalltalk at: #EventSensor put: InputEventSensor

because EventSensor was removed from Pharo, but Magma add some methods
to EventSensor class. I *really* need feedback about the risks of doing
this.

Any feedback is welcome.

Enjoy!


-- 
Miguel Cobá
http://miguel.leugim.com.mx