> | It would be good to have specific rules for configurations.
>
> The Metacello Scripting api is intended to accomplish this particular goal …
I was thinking in terms of Slime for Seaside.
One PhD student is working on rule and I was thinking that it would be fun to
have a kind of
Metacello checker.
do you have some rule of thumb where to look for potential problems?
Because it can be a fun experience.
> the scripting api does not send class-side messages to configurations ...
> with the scripting api, the configuration reverts back to its original role
> of specification and #latestVersion isn't part of the specification.
Excellent
> I think you have produced an excellent piece of documentation …
Thanks but I want more. I ant you to tell me if I do not write something wrong
because people will read it.
> While my english language skills may be better than yours, your writing
> skills are far superior to mine
I do not know. I just write so that I can forget :) I need to release the
pressure in my mind.
> ... I am a very poor writer ... I keep approaching the chapter as a writer
> and I want to completely rewrite things ... perhaps I should just act as a
> fact checker and copy editor?
Sure
Do whatever you want and fit your energy, I just need feedback and I want to
close it.
I refrain myself to change and rewrite the chapter. I would like it to be more
straight to the point but I do not have the energy anymore.
> Pointing out factual errors and correcting the english to the best of my
> ability?
perfect to me.
I need feedback So if you can spot where I wrote something wrong this is what I
need.
If you spot englihs mistakes (I certainly do a lot of them) - please let me
know I will address them.
I have no problem to write. I have problem to write wrong information.
>
> Dale
>
