The closest thing I see in the tutorial (assuming it is working as intended) is a mention of baseline configurations.�� If that is in fact how things can work, there should be an abstract super class for all configurations (or at least a trait they all use to avoid duplicate code) and a method that loads the baseline.

ProfStef would be a lot more useful if it made use of Polymorph: a table of contents in a left pane, select an item and the righ pane shows the content, actions replaced with buttons rather than forcing a lot of right-clicking.�� To the extent that those things are difficult, we need easy-to-use tree models.�� From what I have been able to figure out of the tutorial, a wiki page would be more helpful and more likely to be read.�� If you "force" loading of code, then there should be some benefit in the form of interaction.

My question stands.

Bill

��

---

From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck
Sent: Saturday, February 06, 2010 4:52 PM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Metacello - the missing information??

On Sat, Feb 6, 2010 at 10:22 PM, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:

For any given cofiguration, how does one know which version to load? ��There are incantations in the beginner workspace, but what happens for things not listed there?

You must know about Metacello. As you can noticed, that's why I added the link to the tutorial.
��

Bill

_______________________________________________
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