>> > I don't know. But I think Hillaire had a point in here. what point? We want to change and rewrite all the tools. Now we can only do that with people working. Now we remove the inheritance class browser. and now if you want to see the implementor of add: then you do not use inheritance anymore. You should use implementors or you help in nautilus and rpackage because nautilus implement inheritance.
> There is a change rate a community can cover. As we like to change code it is > ok that things break. If complaints about broken things raise than you should > see that you overstretched your capability and need to think again. Yes but I do not think that we are in this situation. The point is to consider the ratio of changes vs bugs. I can pay Igor one and half year after igor may be forced to sell his PHP skills again :(. So we can go slowly and play cards and watch videos, but this means that less will be done. Or we break some stuff from time to time and this is ok and we move at the speed we believe is good. Right now I'm not even working a day a week on Pharo but if I would work more I would not catch more bugs because these "bugs" are stuff that I never use. So if people use different scenario than us, how can we know it without them raising problems? Stef > The type of replies I replied to just prove that someone is tired listening. > And at least I'm pretty sure that listening is essential. > > Norbert
