If I have to express my wishlist, I would say having a set of trait-
based refactorings is important.
I often realize after having written some code that I want to have
this and that methods in a trait. Doing a right click on a method and
choose 'move method to trait' is useful (with O2). But much more can
be done.
Cheers,
Alexandre
On 10 May 2010, at 10:20, Tristan Bourgois wrote:
>
> I'm working on trait and when there conflicts we can see the
> problematic
> methods. But if you want to see what there are into the methods
> where there
> are the problem you have to do it manually.
> So why not create a mini browser to:
> 1)see the code of the methods
> 2)choose the method to keep (so remove the other method)
>
> Like that you can rapidly see what method to keep or simply see the
> methods
> and could reuse the code for an overridden method.
>
> I think that's a good idea!
>
> Tristan Bourgois.
> --
> View this message in context:
http://forum.world.st/idea-for-a-mini-browser-to-trait-tp2165466p2165466.html> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
>
[hidden email]
>
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Locked
