Re: [Pharo-dev] another spotter question

Oh wow! I had no idea you click that area to toggle the preview! This is my point :) Even with the shift hints. At the very least, it needs something more in the shift hints than just a change in background color!

Re: [Pharo-dev] another spotter question

> On 22 Jan 2016, at 11:08, Aliaksei Syrel wrote: > > I was talking about clickable arrow to open preview ;) > Oh wow! I had no idea you click that area to toggle the preview! Even with the shift hints. At the very least, it needs something more in the shift hints than just a change in backg

Re: [Pharo-dev] another spotter question

Le 22/1/16 11:08, Aliaksei Syrel a écrit : I was talking about clickable arrow to open preview ;) Ok I thought that you also talked about the other. For this one, I would just put a little triangular icon on top and going the in same orientation because then this is clear that this is a k

Re: [Pharo-dev] another spotter question

I think that it is really hard to figure out that the arrow is clickable if you do res shift and see it highlighted. I mean, it doesn’t look like a button or anything special… Cheers! Uko > On 22 Jan 2016, at 11:08, Aliaksei Syrel wrote: > > I was talking about clickable arrow to open preview

Re: [Pharo-dev] another spotter question

Hi aliaksei Hi Stef I saw an early version of Spotter with arrows near each item and it was IMHO awful. But still, pencils taste differently for each of us ;) I do not know. May be the arrow should not be on every element but just on the group/category may be the colors should be deemed.

Re: [Pharo-dev] another spotter question

> On 22 Jan 2016, at 10:23, Aliaksei Syrel wrote: > Sorry for long email > I found it rather short and synthetic ;-) At least compared to my recent messages.

Re: [Pharo-dev] another spotter question

Hi Stef I saw an early version of Spotter with arrows near each item and it was IMHO awful. But still, pencils taste differently for each of us ;) I can agree with you that people "do not get how to use spotter". However it depends on how we define "use spotter". From my prospective almost all do

Re: [Pharo-dev] another spotter question

On Fri, Jan 22, 2016 at 5:27 AM, stepharo wrote: > > > Le 20/1/16 14:30, Aliaksei Syrel a écrit : > > On Wed, Jan 20, 2016 at 12:59 PM, Ben Coman wrote: >> >> +1. Its annoying that it takes two clicks to dive into categories like >> "Implementors" (one to click an item under the category to make

Re: [Pharo-dev] another spotter question

Le 20/1/16 14:30, Aliaksei Syrel a écrit : On Wed, Jan 20, 2016 at 12:59 PM, Ben Coman > wrote: +1. Its annoying that it takes two clicks to dive into categories like "Implementors" (one to click an item under the category to make the arrow appear, and

Re: [Pharo-dev] another spotter question

On Wed, Jan 20, 2016 at 12:59 PM, Ben Coman wrote: > +1. Its annoying that it takes two clicks to dive into categories like > "Implementors" (one to click an item under the category to make the arrow > appear, and then another to click on it) when it would only take one if > that arrow for each c

Re: [Pharo-dev] another spotter question

On Wed, 20 Jan 2016 at 3:37 AM stepharo 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 mea

Re: [Pharo-dev] another spotter question

On Wed, 20 Jan 2016 at 3:37 AM stepharo 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 m

Re: [Pharo-dev] another spotter question

Yes me too but - discoverability should be improved - a nice way to know if you are right is that students with 1 hour lecture in Pharo can use it because this is what I do. I give a lecture and ask them to code one class. - also writing doc for dummies is good because you have

Re: [Pharo-dev] another spotter question

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,

Re: [Pharo-dev] another spotter question

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 ho

Re: [Pharo-dev] another spotter question

Hi, > On Jan 19, 2016, at 6:11 PM, stepharo wrote: > > Ok I want to find all the implementors that contain the word time. > I type time and I see #implementors as shown in the attachement. > How do I get the full list of such methods? > > I have the impression that I will have to retype the qu

[Pharo-dev] another spotter question

Ok I want to find all the implementors that contain the word time. I type time and I see #implementors as shown in the attachement. How do I get the full list of such methods? I have the impression that I will have to retype the query with #implementors. Now I do not get why I cannot click on t