search

krfkeith / metacello

Automatically exported from code.google.com/p/metacello
0 stars 0 forks source link

Newbie observations on use of Metacello #164

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Ben Coman makes some good points that shouldn't be lost:

  http://forum.world.st/Newbie-observations-on-use-of-Metacello-tp4212946p4212946.html

Original issue reported on code.google.com by henrichs...@gmail.com on 19 Dec 2011 at 5:22

GoogleCodeExporter commented 9 years ago

Original comment by henrichs...@gmail.com on 18 Jan 2012 at 7:06

GoogleCodeExporter commented 9 years ago 
Summary of the post:

`Gofer project load:....` is getting close to something that would make better 
sense, but `Metacello load:....` might be a better alternative even though it 
might just be a cover for `Gofer project....`.

Ben lists a number of the Gofer project features that he likes[1]... Which 
makes think that the command line interface would gain from wrapping some of 
the MetacelloToolbox api, too.

Another advantage of `Metacello load:...` is that it would provide an 
opportunity for Metacello to have a presence in a base image ... which means 
that the ensureMetacello would be built-into all images ... which means a 
common superclass for configurations could be included .... worth thinking 
about a little bit

[1] 
http://forum.world.st/Newbie-observations-on-use-of-Metacello-tp4212946p4218364.
html

Original comment by henrichs...@gmail.com on 26 Jan 2012 at 10:12

GoogleCodeExporter commented 9 years ago

Original comment by henrichs...@gmail.com on 27 Jan 2012 at 9:39