You see I complained a lot about Spotter but I do not care about the order.
I care that I can use it and be told how to use it.
As a newbie programmer I want to get the feel of going fast. I do not want that
after the 1 hour of Pharo I'm told that I can look inside the implementation to discover something.
First I need a system that shows me what I can do then when I get fluent in Pharo I can
start to think about looking inside.

Stef the poor guy that is writing documentation for dummies.

PS: I want to program with my 15 y old son and that he can program by himself not me doing
magic incantation.

On 19 Jan 2016, at 15:23, Esteban A. Maringolo <emaringolo@gmail.com> wrote:

It turns the search field into a "kind of" command line interface, with #sen/#ref as commands.

I love CLIs so I welcome it, but I think It "perverts" the search field and uses an awkward syntax. I prefer to type "senders" than to type a special character like #.

I would prefer adding a suffix command so you search for 'do: senders' or 'do: implementors���.

just that there is no syntactical way to know when you want senders or just retrieve methods who start with do: and continue with keyword sen��� etc.

that���s the reason from the hashtag (which is now a common symbol to filter/tag like in twitter/facebook/etc.)��

cheers,

Esteban

Regards!

Esteban A. Maringolo

2016-01-19 10:43 GMT-03:00 Tudor Girba <tudor@tudorgirba.com>:

Hi,

With the latest GT integration, we also integrated the search for senders and references from the first step.

Here is a detailed explanation about it, including what we still want to do, how it���s done, and how to discover what else is around:

http://www.humane-assessment.com/blog/spotting-senders-references-with-gtspotter/

<spotter-senders.png>

Please let us know what you think.

Cheers,

Doru

--
www.tudorgirba.com
www.feenk.com

"Problem solving efficiency grows with the abstractness level of problem understanding."