Bill, With the next release of Metacello I am planning to include a scripting API where you will write scripts like the following: Metacello new project: 'Seaside30'; load. or: Metacello new project: 'Seaside30'; squeaksource: 'MetacelloRepository'; version: '3.0.6; load: #('Base'). for more examples and some discussion see[1]. The API is still under development and if you (or anyone else) would like to comment, I suggest that you join the metacello group[2] and join the discussion. The Metacello class is intended to be included in the base image of Pharo, GemStone and Squeak, which would allow for cross-platform scripting. Dale [1] http://forum.world.st/Metacello-Scripting-API-strawman-td4334979.html [2] http://groups.google.com/group/metacello ----- Original Message ----- | From: "Wilhelm K Schwab" <bschwab@anest.ufl.edu> | To: pharo-project@lists.gforge.inria.fr | Sent: Tuesday, February 7, 2012 8:12:14 AM | Subject: [Pharo-project] Building images | | | Friends, | | I know it's not a popular position, but I consider Metacello to be | poorly factored, unstable, and a bit confusing. How many times do we | type things like: | | Gofer new | squeaksource: 'Fuel' ; | package: 'ConfigurationOfFuel' ; | load . | ( Smalltalk at: # ConfigurationOfFuel ) load . | This is concise, but it is also arguably syntactic sugar. I have been | trying to condense the redundant information, and have been (trying | to) capture the details in a tool I call Migrate. I have filed out | the main class (attached). The idea is that one can save the Migrate | package, load that into a new image, and quickly configure the new | image. At least that's the plan. | | Of interest now are the helper-metacello methods. What do you think? | I'm trying to help here... | | Bill | | | | | | | | | |