Just now, I've been looking into http://code.google.com/p/pharo/issues/detail?id=1570 I've reported last week.�

I was using the dev image for this. I'm not using the Core image, since there I'm missing essential tools I need.

The error was that in the system browser �browse package did not work anymore.�

I've looked into the issue , the cause of it is that Lukas updated Refactoring-Core-lr81.mcz, adding:� 'the package environment can work on multiple packages now'; thereby deleting the package message, replacing it by the packages message. Of course the OR2EnvironmentNode>>packageCategories which failes is still using the package message, and not the new one.�

I can off course quickly fix it by adding packages first or something, but that is not the point I want to make. The point is that a development environment should be stable. I'm also not judging or finger pointing or anything. I'm just giving an example to indicate that this is not good, that essential behaviour just from one version to the other can break and we don't even notice it, till someone tries it. And figuring a bug which cause was almost a month ago is more difficult and takes a lot more of our precious time than noticing it directly.

So again also my question: is there a way to for instance test that if I open a SystemBrowser, navigate to a class, and execute the browse package command that a package browser window is opened on it; so like this I can test if any regression took place.

If I look at the milestones for 1.1 I notice that there is�a Continuous integration system planned. This is good, very good, actually essential. We should really try to do Continuous Integration, even in the development 1.1 branch; more forward in small but certain steps.

Kind Regards,

Bart

On Fri, Dec 18, 2009 at 10:19 AM, Marcus Denker <marcus.denker@inria.fr> wrote:

On Dec 18, 2009, at 9:41 AM, Bart Gauquie wrote:

> Dear all,
>
> I've been using Squeak before, now I'm using Pharo. Its still 'hobby' usage. However, on my firm, we have a lot of working groups in which we investigate new technologies. We mainly use Java / .Net.
> I've initiated a working group around Smalltalk/Seaside. And chose Pharo as a smalltalk platform/dialect, mainly because its free and adaptable. I'm a fan of it, but my colleagues of it have some doubts about it. I know that its not finished yet, and that a lot of improvements are ongoing. The main 'complaint' about Pharo is that the environment is not stable. In a lot of the tools you get exceptions, errors, it breaks something, stuff like that. Thats a shame off course. I expect in an environment that everything just works. We are using Eclipse in our day to day work; nowadays, Eclipse is quite fast and is reliable. Pharo is more or less fast enough, but still not reliable. There are too much 'dead links', messageNotUnderStoods I mean. For instance on latests browse package is not working on the Class Browser. On the Pharo 1.0 branch, there are also dead links here and there.
>

1.1 can not be stable. How on earth can you do anything if even the bleading edge developement-only release can not move?

Do *not* use 1.1 if you are not willing to live with a bug *and* are willing to help fixing it.

If you see bugs in 1.0, How Can We Fix them if they are not reported?

� � � �Marcus
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project