Miguel Enrique Cobá Martinez wrote:
I don't dislike Squeak usage but changing a emerging technology that is being used in a given way and that appears to be working (I've done the Magma configuration and I tested it worked on Squeak and Pharo) but this new Squeak usage of Metacello really discourages to try to keep the Magma for other distros than Pharo. It really is a gratuitous change and I don't really have the time to sync two ways to use the same technology.
Miguel, I'm not going to defend how the Squeak folks are using Metacello, but I will say that they have a slightly different use case and they are currently exploring the possibilities in support of that use case. For the moment I would take a wait and see attitude, while continuing to maintain your cross-platform configurations. Think of your users...Magma is used on both Squeak and Pharo and a cross -platform configuration _is_ the best way for you to publish the information... In the absolutely worst case scenario (i.e., impossible to load the Magma config because of class name conflicts) it will be possible for your users to unload the "configuration package" and use your config, then reload the "configuration package". Hopefully, the Squeak folks will settle on an approach that is compatible with cross-platform configs without requiring drastic measures... Dale