Hi, > On Jan 19, 2016, at 6:17 PM, stepharo <[email protected]> wrote: > > >> >> Essentially, #Selectors behaves like completion and it allows you to >> discover new selectors. What’s more, if you trigger the action (Enter) on a >> selector, you get the implementors browser for this selector. >> >> Does this make sense? > Not really. It looks really complex to remember. > To me selectors is part of implementors. I find it confusing.
I am not sure I understand. Here is the reasoning behind the names. Perhaps we can find better ones: - The Implementors Browser shows methods implementing a selector. - So, from this point of view, an implementor is a method. > How do you get the right pane opened? > Because I cannot get it. > I clieck on the check or the arrow but it does not open. On which arrow? :) When I tested the UI with users, and there were some, all of them felt that the gray arrow that goes outside the border is strange, and they clicked on it to see what it does. It seems that you do not see it like that. Perhaps the contrast is not strong enough, and we can work on that. And then, in Spotter we have another discovery mechanism: Shift. When you press it, all clickable things get highlighted (including the arrow). We chose Shift because it is something that you type often as part of a text, so it will be very likely that you will press it when working with Spotter as well. And this will get you to see that something happens. > Again another discoverability problem. I think that my remarks about how to > learn spotter > still stands. Yes I can read your blog and may be remember everything but > this is the way > UI works. Thanks for describing your way of working. It is useful. In any case, a help would certainly be useful, and it is on the todo list as well. Cheers, Doru > Stef > > -- www.tudorgirba.com www.feenk.com "It's not how it is, it is how we see it."
