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.
Thanks Miguel, you have definitely done better than I ever did at making a clear, coherent, clean installation. Your solution to the FlapTab warning is creative, although I'm curious whether it was possible to simply handle the warning in the load-script and resume it? Ah, one bad aspect of simply handling / resuming Warning is that it would tend to hide any future warnings about other classes (which might be important)..
Also, I'm curious about why it was necessary to capture and restore the underscore-assignment setting for 1.1r2. Did I miss some underscores or is that only to support loading older Magma versions in 1.1?
- Chris
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
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
El jue, 05-08-2010 a las 20:57 -0500, Chris Muller escribió:
Thanks Miguel, you have definitely done better than I ever did at making a clear, coherent, clean installation. Your solution to the FlapTab warning is creative, although I'm curious whether it was possible to simply handle the warning in the load-script and resume it? Ah, one bad aspect of simply handling / resuming Warning is that it would tend to hide any future warnings about other classes (which might be important)..
Yes it occurred to me too to use something like that but as I didn't know how to do it I prefered to create an empty class and then delete it.
Also, I'm curious about why it was necessary to capture and restore the underscore-assignment setting for 1.1r2. Did I miss some underscores or is that only to support loading older Magma versions in 1.1?
No, it was because versions previous to 1.1r2 had underscores and to load them I wanted to restore the user preference after installing Magma. In 1.1r2 it isn't really needed, it was too late at night :) I will remove it soon.
Cheers
Hi,
From a fresh install of Pharo 1.1 and only after loading Seaside, when I
evaluate
Gofer new squeaksource: 'UniverseForPharo11'; package: 'ConfigurationOfMagma'; load.
in a Workspace window, I get the following error
GoferRepositoryError: Could not access http://www.squeaksource.com/UniverseForPharo11
(newbie here so please go easy on me)
In an attempt to address the above, I created
MCHttpRepository location: 'http://www.squeaksource.com/UniverseForPharo11' user: '' password: ''
but when I attempted to open the repository, the error window was titled: "Error: Could not access http://www.squeaksource.com/UniverseForPharo11"
Would you help me understand what I'm doing wrong?
- Marco A.
Sorry, ignore my previous post... I found the answer in http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg31841.htm...
magma@lists.squeakfoundation.org