On Fri, Apr 10, 2015 at 7:44 PM, Sean P. DeNigris <[email protected]> wrote:
> Ben Coman wrote > > I believe #asClass itself was introduced for a use case to simplify > > Workspace "user interactive" Gofer scripts to retrieve and load > > Configurations. > > Yes. But it's no longer necessary due to... > > > Ben Coman wrote > > extended Gofer with a method #configurationOf: > > We already have this :) > > Gofer it > ... > configurationOf: 'MyCoolProject'; > loadStable. > > So there is no conflict: > 1. Use the new Gofer API in the workspace (or the Metacello one Christophe > pointed out) > ahhh, cool. The rest sounds fine then. cheers -ben > 2. Handle dependencies like we did for decades prior to #asClass ;) > 3. Remove #asClass before it poisons our beloved system!!! >
