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
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
