Hi, I was not arguing with you :).
You asked how to find the answer to help you write something, and I replied how to get the information. I am not saying that this is the best way. It’s only the way it is. Doru > On Jan 19, 2016, at 9:24 PM, stepharo <[email protected]> wrote: > > Doru I know that I can be a power user. > This is not the point I want to make. > The point I want to make (I know I'm dense) is how normal people under stress > because > - they learn > - or are doing a task > can learn and discover. > When I'm hacking my business I do not want to browse a blog post. I want my > job to get done and get home. > > Stef > > > Le 19/1/16 14:46, Tudor Girba a écrit : >> Hi, >> >> It’s not magic :) >> >> You can directly query this programmatically. >> - Find all processors defined in the image: >> GTSpotter spotterExtendingMethods >> - Find the top level processors defined in the first step >> GTSpotter spotterExtendingMethods select: [ :each | each methodClass = >> GTSpotter ] >> >> You can find some more details in the last post: >> http://www.humane-assessment.com/blog/spotting-senders-references-with-gtspotter/ >> >> Does this make sense? >> >> Cheers, >> Doru >> >> >>> On Jan 19, 2016, at 12:36 PM, stepharo <[email protected]> wrote: >>> >>> Hi >>> >>> I was stupid enough to write in the book that #method is for methods. but >>> this is for #implementors. >>> So how do I get the list of categories in Spotter? >>> Magic? >>> >>> Stef >>> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Not knowing how to do something is not an argument for how it cannot be >> done." >> >> >> > > -- www.tudorgirba.com www.feenk.com "Every thing should have the right to be different."
