Hi, > On Jan 19, 2016, at 9:18 PM, stepharo <[email protected]> wrote: > > > > Le 19/1/16 20:25, David Allouche a écrit : >> BTW, thanks for the explanations for Spotter.
You are welcome. Please keep challenging. This is how good design happens. >>> 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. What is RSI? Most people I know use Shift to type an upper case, and we observed that when people search, they often tend to still use uppercase. Not all, but many. That is why we put this functionality on Shift. This does not mean that it is enough, but we just wanted to increase the chance of people stumbling across this without any documentation. It only partially succeeded. Anyway, we should externalize the key bindings. Another thing on the to do list :) >> 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. #Messages is not a bad name, but then again I also thought that #Selectors was explicit enough :). What do others think? >> 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 Left/Right is used to move inside the text area (there is only one text field in the whole UI), and that is why you cannot consistently use it for navigating through results. Navigating when the cursor is at the end is a tempting idea, but it implies a mode that is not contextual (you need to things to look at). That is why I would not want to have it in this interface. >> >> 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. We explicitly chose not to do that because we did not want to mingle different kinds of elements in the same list. So, like this, when you press Cmd+Right, you will always dive in one single element, and not in many by mistake. Actually, our original goal was to have a way to expand the list in place (not only to dive in category). For this we wanted a … line and clicking on that would expand the list in place. We did not get to do it yet, but I think this would solve quite some of the reported problems. But, please do keep challenging. And give it a try with writing your own processors. It would help us a lot. Cheers, Doru >> That would be awesome. -- www.tudorgirba.com www.feenk.com "Obvious things are difficult to teach."
