Hello In my case, I would like to see USED (ie. not removed or replaced) trait methods by default with clearly visible mark that they come from trait (which is how Nautilus presents them). Reason is that quickly seeing whole API brought by this class is more important to me than seeing what the class actually imprements. I would LOVE feature to hide trait methods. I have few classes with like 20 trait methods and 2 own ones and it would be great to temporarily switch to see just the 2 (but when I open the class again later I would like to see all of them again). It seems to me there ought to be multiple opinions on this, so having option in settings (to show trait methods or hide them by default) would be best solution for both groups. Jan Denis Kudriashov wrote
Hello.
In next Calypso version the option to enable or disable trait method visibility will not be available anymore (not my choice). All trait methods installed to the class will be just a class methods like it was in Nautilus. No way to hide them. I want to ask you what you think about it. - do you prefer to see trait methods by default? - do you want feature to hide trait methods?
Current Calypso support for traits follows simple principle which I found important for me. But I can be the only guy who think this way. Maybe because I meet traits in Self. So: I simply want to see in the browser what class is actually implements. If class uses TEmpty trait (with ifEmpty, isEmpty methods) I don't want to see its methods by default. When I open such class in the browser I want to see only code which class explicitly implements For me this logic is same as for superclass methods. It was my original intention for trait support in Calypso. And I would like to hear if people share it or not. (there are missing trait feature in the current approach but it is not a subject of my question. Think that everything is supported correctly)
Best regards, Denis
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html