Stef, I think so ... I think that when we get to the point where we have separate Metacello repositories for Pharo 1.0 and Pharo 1.1 it will be part of the 'require' tool set anyway... Dale Stéphane Ducasse wrote:
so may be we should load it with metacello / gofer?
On May 27, 2010, at 8:37 PM, Dale Henrichs wrote:
Stef,
That's exactly what GoferProjectLoader is for... see http://www.smallworks.com.ar/en/community/GoferProjectLoader.
Although you'd type:
Gofer project load: 'Torch'
Dale
stephane ducasse wrote:
hi lukas recently I spend a lot of time typing expression like that Gofer new squeaksource: 'Torch'; package: 'ConfigurationOfTorch'; load Gofer new squeaksource: 'Glamour'; package: 'ConfigurationOfGlamour'; load And I would love to type Gofer loadConfigurationOf: #Torch is it possible :) Stef _______________________________________________ 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
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project