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.
I do not think that having a query for something that we do not use is
good.
I look for implementors and I'm used to get a list of methods
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.
I never thought about clicking on it. I thought it was a decoration not
an active element.
It seems that you do not see it like that. Perhaps the contrast is not strong
enough, and we can work on that.
I see the arrow but it does not have an icon so why should I start to
click on everything to see if it
reacts. This is not the way I use User Interface. In general the UI
tells me where I should click
and I click. I did not ask the question to be dum or to show that
Spotter UI is not intuitive: I could not find how
to get the pane.
So this is totally obscure that the arrow is more than a decoration.
Putting an icon inside
would make the trick because all the other parts the clickable once have
icons.
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.
Seriously not!
Because you do not see how my hands are on the keyboard (we compared
with esteban) my hand is fully over the keyboard
with my tiptoe on numbers and higher like fn key so pressing shift =
pain to me because shift is near to my wrest. In general I do not use
shift. This is shift+ enter does not work for me. I would like to have
esc + enter because esc is on the top left and I have my finger often on
it.
The proof is that I never saw that shift had any meaning and as I told
you when I started to use Spotter
I got pain in my hand => STOP using it.
Damien has pain in all his fingers and looking for the reason (and the
reason may be emacs shortcuts) so I do not play with
strange short cuts.
I started to use Spotter when I saw that I can use the right shift below
enter.
Now shift + cmd + arrows is nearly impossible because those are all keys
at the bottom of the keyboard.
So at the end what you believe is handy is handy for certain people but
not other. I will not change my hand over
keyboard position because I'm really efficient with it and I have no pain :)
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.
Yes and it does not have to be perfect and a menu to reset it.
Cheers,
Doru
Stef
--
www.tudorgirba.com
www.feenk.com
"It's not how it is, it is how we see it."
