On Thu, Dec 31, 2009 at 1:19 AM, Adrian Kuhn <akuhn@iam.unibe.ch> wrote:
Lukas Renggli <renggli@...> writes:

> Then somebody that uses OB and Traits daily should commit on that. I
> am not a trait user, so I can't help here. The same for the package
> browser: I am pretty happy with OB, the package browser of
> OB-Refactory, and Gofer to manage the 75 Seaside packages.

+1 yellow browsers are awesome to work with packages!

NB: when you halo-copy-paste the menu items to open your most used packages
�to the background and rename them to the package name, then you even get a
�1-click way to open your yellow browsers.

I work one hour a day with one trait :) will do my best to report all bugs I
�find. There is not much, and most of them can be fixed by adding #superclass,
�#isVariable and #parseTreeFor to TraitBehavior. See my fix for issue 1666

Other than OP, I find the 1.0 dev image rather stable (mebbe OP is speaking of
�1.1 dev image ???).

What's OP ?

Depending which version are you talking about. 10496 seems to be very stable for me. I have been using it 12 hours a day for the last 20 days and no problem except the double copy paste. With 10502 I cannot even click on a class neither in the code panel. Look the opened issues:

http://code.google.com/p/pharo/issues/detail?id=1182
http://code.google.com/p/pharo/issues/detail?id=1724
http://code.google.com/p/pharo/issues/detail?id=1721

The one thing one has to do to get a stable dev image is
�to *revert* the loaded OB-Refactory package to the loaded version such that O2
�clutter is reverted to the right OB methods. Mebbe changing the load order
�when creating the dev image might help to avoid that issue.


Adrian, would you mind explaining a bit more in details this problem ?

Thank you very much.

Mariano

Else I am totally happy with the dev image.

--AA



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