haha, I see that Esteban has gone much farther towards creating a set of tools that go way beyond the simple loading of a configuration ...
Dale ----- "Dale Henrichs" <dale.henri...@gemstone.com> wrote: | ----- "Alexandre Bergel" <alexan...@bergel.eu> wrote: | | | A minor comment: | | | | > Gofer new | | > squeaksource: 'MetacelloRepository'; | | > package: 'ConfigurationOfPharo'; | | > load. | | > | | > ((Smalltalk at: #ConfigurationOfPharo) project version: '1.0- | | > rc2.10505') load. | | | | | | I find this incantation quite ugly. | | Alexandre, | | How about something like the following expressions: | | Gofer loadConfiguration: 'Pharo' version: '1.0-rc2.10505'. | Gofer loadConfiguration: 'NewInspector'. | Gofer loadConfiguration: 'Magritte' load: #( 'Magritte-Model' | 'Magritte-Tests' ). | Gofer loadConfiguration: 'OmniBrowser' version: '1.0' load: 'Core'. | | I whipped together some extension methods for Gofer that adds support | for the above to Gofer: | | Gofer new | gemsource: 'metacello'; | package: 'Metacello-Gofer-Extensions'; | load. | | If there is no leading ConfigurationOf in the configuration name, | 'ConfigurationOf' is tacked on. If no version is specified (or is nil) | the latest version of the configuration is loaded. If no explicit load | list is supplied (or is nil), then the default load list is loaded. In | all cases it is expected that the configuration will be found in the | MetacelloRepository on SqueakSource... | | Dale | | _______________________________________________ | Pharo-project mailing list | Pharo-project@lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project