Sean, In my last post, I provided my vision of the future ... for the present, the answer is "what you see is what you get" ...
When a new version of Pharo comes on the scene, the challenge is to port the existing configurations to the new version ... it does not happen magically and it does not happen over night and it does not happen without old fashioned effort ... When a new version of Pharo identifying configurations that don't work in the platform is a necessary task... it's no different than a bug in the base class library: feature x does not work configuration y does not load It would be nice if software and configurations could be written without bugs or could be written once to run on all conceivable future versions, but this is not the case ... Defining a #stable version for pharo1.4.x is a good way to indicate that the configuration has been ported to Pharo1.4 and loading the #stable version of a project is a good way to get the correct version of the project based on which platform you are on. If loading the #stable version blows up, that sounds like a bug to me, either in a configuration or the software itself ... If you don't want to experience the pain of developing on a new platform, then don't move to the new platform until the hubbub has died down ... Dale ----- Original Message ----- | From: "Sean P. DeNigris" <[email protected]> | To: [email protected] | Sent: Friday, April 27, 2012 9:08:17 PM | Subject: Re: [Pharo-project] What about making the configuration browser more visible? | | | Schwab,Wilhelm K wrote | > | > Put another way, if it's that simple, why all the contrary | > instructions | > over time? | > | | I understand your frustration. We are like parents watching a child | grow | up... | | For one thing, the API has been evolving as we've learned. From | loadLast/Latest, to bleedingEdge/development, now to symbolic | versions | (which were sorely needed). | | The other impediment was that Metacello couldn't be assumed to have | preloaded any base classes. Thus, ConfigurationOfXxx classes rely on | someone | manually (or automatically via tools) adding convenience methods. | Without | these, the API is hidden away in the project class. | | Recently, there seemed to be some agreement between Squeak and Pharo | to load | some base Metacello classes. If Configs had a common subclass, I | think the | system browser would be much more helpful. | | Dale, what do you think about all this? | | HTH, | Sean | | p.s. of course ultimately, success depends on people testing projects | and | updating the configs... | | -- | View this message in context: | http://forum.world.st/What-about-making-the-configuration-browser-more-visible-tp4590573p4594228.html | Sent from the Pharo Smalltalk mailing list archive at Nabble.com. | |
