I also struggle with Spotter, I learn something new all the time. I also use Spotter all the time.
I understand that there is great value in starting from a couple of simple principles and see how they can combine in many different ways. Something with good internal logic is easier to explain, use, maintain, evolve. Spotter is quite different than the other tools that we had before, for me it feels more like the Google search field. It is not possible to have a totally obvious interface, no more than a code browser or a debugger, or programming can be self explaining. Of course, we should try to make it better if we can. I am very happy that we have something as powerful and advanced as Spotter (and its family). I think we are totally on the right track. > On 19 Jan 2016, at 20:30, stepharo <[email protected]> wrote: > >> >> Hmm. Thanks for describing this way of working. >> >> Here is the thing. We observed users working with this, and they all used >> predominantly the keyboard. So, we favored keyboard use. This is not an >> argument for anything, and it does not mean that that is the best design, I >> am just telling you how we designed it. Things can change, and this is why >> it is important to understand how people tend to use the UI. >> >> So, every (and only) selection has actions. In your example, the #Menu >> category has a right arrow next to it. If you click on that you “Dive in >> category”. That means that if you want to dive in #Implementors, you >> navigate there, and then you get the option of diving in. >> >> We consciously chose to not show all actions all the time because that would >> have led to an overcrowded UI with too many things to choose from. Right >> now, you have 5 main things to click on and that is it. >> >> Now, hearing your scenario, it seems to make sense to make the category >> clickable as well and make it dive in that category. We will look at it (or >> maybe someone else does it beforehand :)). Thanks. >> >> Does this make more sense now? >> > > Yes! I do not get why keyboard is orthogonal to direct access. > > To me what I hate in UI is UI that are showing information but do not let you > access it. > > How can I see that I can do something on the list? > The arrows only arrive when I click on ........ > So I was trying to click on the label and it did not work. Of course I > must click on the first element > of the list so that the arrow show up on the element and the label!!!!! > > What??? > > Seriously doru. You should have asked UI blind like me to test Spotter. > I would have recorded a session and you can see that there are glitches > that you do not even see. > I'm just continuously bumping on them. > This is why I could understand Spotter and use it only to find a class. > > > > > <adhaefha..png> > > > > This is why I like the grabbing possibility of file on mac via the icons and > the navigation from there > because I see the file it is in front of my nose and I do not to jump into a > file system (like a mail download folder > I have no clue where it is) to grab it. > So to me Spotter should offer the same. Show information and let me grab it. > Especially when this is on the suggstion > list. > > I do not understand how you solve the problem I got with shortcut btw. > > You see the point is the following. Diving can be frustrating. > If on click on the labl you get the list then it can work really well. > >> Doru >> >> >>> Stef >>> >>> >>> >>> <icfedjib..png> >>> >> -- >> >> www.tudorgirba.com >> www.feenk.com >> >> >> "When people care, great things can happen." >> >> >> >> >> >> >> > >
