On Jan 10, 2016, at 12:21 AM, stepharo <stepharo@free.fr> wrote:
Doru
are all the type after the name?
menu #pr
No. You can also do it like this:
#pragma menuI always thought it was the inverse.
Where can we find the list of #�
That depends on the place you are searching.
The # searches through the categories defined in the class of the current step. By default, you start in an instance of GTSpotter so you will find methods that are annotated with <spotterOrder:>. All extensions of for GTSpotter are documented by inspecting the GTSpotter class (and you can filter by the name of the class):
So, # does not define a search action. It filters the search results that happen anyway. That is why it is probably more natural to first search what you are looking for, and then trim to only see the category you are interested in. In any case, you can do it both ways.
Why we cannot have a ghost showing one example.
What do you mean?
Blog posts are not part of the discoverability of an UI.
Of course they are not. But, this is a bit of an unfair comparison :).
Doru
Stef
Le 9/1/16 22:42, Tudor Girba a �crit :You can find documentation with examples about GTSpotter on the humane-assessment.com blog:
https://www.google.com/search?client=safari&rls=en&q=site:humane-assessment.com+gtspotter&ie=UTF-8&oe=UTF-8
Specifically about finding Pragma usages, I just added a blog post:
http://www.humane-assessment.com/blog/spotting-pragmas-with-gtspotter
Cheers,
DoruOn Jan 9, 2016, at 11:00 PM, stepharo <stepharo@free.fr> wrote:--
Hi
Is there a help a student or idiot like me can read about how to find information with Spotter?
For example
We with luc wanted to find all the senders of variableSubclass: we tried # #senders and more... but gave up.
Yesterday I wanted to find all the user of <menu>
May be I missed an obvious help that will enlighten me?
I hope.
Now without such help how can we expect students or users to discover the way we should
use the tools?
We were planning to do a video to explain Spotter but I'm slowly thinking to discard this video
because we do not know.
Stef
www.tudorgirba.com
www.feenk.com
"Value is always contextual."