On Dec 9, 2010, at 3:53 PM, Chip Nowacek wrote:

Hello everyone,

While I should have introduced myself before I ran into trouble, it is trouble that has brought me here. I guess I'm glad something provided the excuse to meet you.

First, a short introduction...

I'm really new to Smalltalk. Kent Beck said it's a good choice for my project. Technically, I come from the database architecture world - though I am more entrepreneur now than techie. I'm starting up a new company and Kent suggested building a prototype myself instead of bringing someone else in - so here I am. I'm trying to move from Squeak because Pharo feels a little more developer oriented. We'll see how it goes.

To the matter: I don't understand why I can't accept a change to my comment in one of my classes. When I try to accept in the OB Package Browser, about a dozen calls in, #Utility is being sent #changeStamp and doesn't understand it. I am in the midst of sorting through the stack trying to figure out what happened. As you might imagine, it's a little discouraging for such a basic function to blow up. What makes it worse, I'm probably the cause of the problem - I just don't know what I screwed up. I am working in Pharo 1.1.1 and have loaded Magma and O2 per:

Hello, We did not include O2 in the release precisely because it it not yet mature enough... it has lots of nice features and I understand that people want to use it. But man-power was not there to bring it to a state where all these bugs are fixed. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.