Hi Stef, > On Jan 10, 2016, at 10:21 AM, stepharo <[email protected]> wrote: > > Hi doru > > you see I make the effort to reply even if I get really frustrated with our > tools.
Thank you. First, let me say that I was not arguing at all. I was looking for solutions. The way I know to do it is to make explicit the reasonings that we already went through so that others can poke holes at it. I also wanted to say that the choice was not random, but maybe we can find a better choice. > I do not get why you cannot > - have a set of fixed most used queries and this will create a small > vocabulary that can be extensible > and it can be mapped to what we do with shortcuts = reduce cognitive load > and then a full search when you do not know what you are searching. > This is not exclusive and it works for the two scenario. I understand the intention, but I do not understand how these fixed queries are any different than we have now. When you are on the top of Spotter, when you query, you get always the same processors being executed. At first you will not know their names, and you will scroll. And if you see them, you might remember them and reproduce afterwards. It’s a discoverable learning process that you do not have to remember. The only part that is not discoverable is that # introduces a category search. Thinking loud, I just thought that we can make the label start with # like this (I committed this change): We also thought of having completion as soon as someone type #. So, you have a kind of a dropdown for the available categories, but we did not get to implement that one. This should solve the discoverability problem even more. What do you think about that? Regarding the shortcuts, we could associated such shortcuts with a processor, but I would first want to see if we cannot manage to produce a solution with the current set of options. > I was discussing with Luc and he made a fun but sad remark > "Since people do not understand well spotter they most of the time only > use it to open a class. > And this is something that he already had before." > I briefly looked at the Youtube video of Chloupis and > So you can have a generic super cool tool, if people do not use it it defeats > its purpose. Certainly. > You can be really happy because you go fast with it but you only. That is not really true :). > So making sure that the most used actions are really supported is important. Of course it is. For Senders we did not find a good solution yet that is reasonably fast and useful. Stefan and I are still literally working on this. I think we should be able to have a solution, but we have to see if it is reasonable enough. We will announce it once we have it working. But, really, this tool more than anything allows one to play with possibilities in a couple of lines of code. We want people to play (some did) and to get concrete feedback and possible solutions. I think we should not just say that we need something else before we actually play with it a bit more. > But more important the discoverability is important because there is not even > a help. > Right now as a user I can only guess and often I close spotter and use my > shortcuts. > As a user I see something that ask me about network (and I do not care) but > nothing > that brings me to the next level. This is something we need to work on, but you know, time is limited for us, too. > Most of the time the user forgets the key combination (may be this will be > solved with > the cool shortcut reminder we developed and is under review) All actions in spotter have a visible icon. All. And if you hover over it you get the command. And there are literally 5 such actions. What is missing in this regard from your point of view? Doru > Stef > > > > -- www.tudorgirba.com www.feenk.com "Reasonable is what we are accustomed with."
