Le 19/1/16 20:25, David Allouche a écrit :
BTW, thanks for the explanations for Spotter.
On 19 Jan 2016, at 18:37, Tudor Girba <[email protected]> wrote:
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.
I am lazy and fearful of RSI. If I can avoid using the shift key at all, I am
quite happy. So I did not notice that the arrows where clickable.
:)
Same here.
Here are a few suggestions that would fit my workflow.
I also think that "Selectors" should appear after classes and before packages, and be
called "Messages". Typically I want to open a specific class, or a specific message in a
specific class.
The short list of implementors at the top level is usually noise and might have
confused Stef. It becomes relevant once the message is fully specified.
Diving in should be done with right arrow when at the end of the command line.
Diving out with left arrow at the start of the command line.
I was wondering what is the benefit to have cmd - shit arrow vs arrow
When a list of paginated (only first N items), then the category line should be
accessible with arrows, so we can dive into a category just with arrows.
That would be awesome.
