Well my point is that if I see a button I know it will do something.

If I see a label I will ignore it, because it's just a label. I don't think it's a good UX to make it clickable.

(The only reason why Class side can get away with it is because there's checkbox next to it).

On Sat, Aug 1, 2015 at 1:25 PM, Franck Warlouzet <franck.warlouzet@hotmail.fr> wrote:

Hello,

Yes it looks a little bit 'lite' but we did not want to have 2 buttons with the same look but two different kinds of actions. Hierarchy button changes the window itself and variable and scoped open a new menu or window.

I agree about the class side button.

Franck

Date: Sat, 1 Aug 2015 12:26:02 +0200
From: i.uhnak@gmail.com
To: pharo-dev@lists.pharo.org
Subject: Re: [Pharo-dev] Nautilus new buttons not buttons?

Speaking of buttons... The Hierarchy/Flat button and [] Class side isn't entirely consistent either.
And since everyone is used to it by now nobody will want to change it. :)

On Sat, Aug 1, 2015 at 12:21 PM, Peter Uhn��k <i.uhnak@gmail.com> wrote:
Hi,

why are the new nautilus buttons not buttons?

��
They look like labels which is confusing.

Peter