I think that by default methods coming for traits should be visible in the browser, but needs to be somehow identified.��

Pharo traits was conceived in a way that from the class point of view you see no difference if it was flattened or not, and Self traits are not exactly the same because they use the delegation scheme in the method lookup.��

I think that a feature to hide trait methods is unneeded, but the possiblity to easily filter methods coming from a trait it a good one.��

Just my two cents.

And by the way, we really need to name traits with a T in the name? I always found this ugly, it makes the trait support look like a hack.

On Wed, Oct 10, 2018, 19:40 Denis Kudriashov <dionisiydk@gmail.com> 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