Hi, > On Jan 19, 2016, at 6:14 PM, Esteban Lorenzano <[email protected]> wrote: > > It has to be the oposite: > > #implementors should show what people understand until now (a list of > implementors) > #methods should show the actual methods (as now does #implementors)
Hmm, I think I do not understand so please bare with me. You seem to suggest that #Implementors would show selectors (symbols), and #Methods would show . > why complicate things if we can do it in a way that satisfaces everybody? The goal is certainly not to confuse. Only that the problem is a bit more complicated than what might appear. When you are inside a method, you will naturally want to see #Implementors and #Senders. And in both of these categories, you will have methods and the preview will show code. If on the top search, #Implementors will just be symbols, then we have two meanings for the same label. We could also use #Methods and #Senders when inside a method, but that would not match well either. So, that is why we use #Implementors in the top search. Does this make more sense? I am asking because these are not carved in stone :) Cheers, Doru > Esteban > >> On 19 Jan 2016, at 18:07, Tudor Girba <[email protected]> wrote: >> >> Hi, >> >>> On Jan 19, 2016, at 5:52 PM, stepharo <[email protected]> wrote: >>> >>> Doru >>> >>> on the blog you mention selectors but I'm confused, I thought that methods >>> were implementors. >>> So what is selectors? I checked and they are methods too. >> >> So, the difference is as follows. >> >> #Implementors lists actual methods. For example, if I search for do:, I will >> get multiple methods implementing do:. Also, when you preview, you get >> directly the source code of the method. If you trigger the action (Enter) >> you get the code browser opened on the method. >> >> <a GTSpotterMorph(804686592)2016-01-19T18-00-41-751893+01-00.png> >> >> #Selectors, will show only one occurrence of do:, and when you preview it, >> you see the list of implementors. >> >> <a GTSpotterMorph(804686592)2016-01-19T18-00-47-165509+01-00.png> >> >> Essentially, #Selectors behaves like completion and it allows you to >> discover new selectors. What’s more, if you trigger the action (Enter) on a >> selector, you get the implementors browser for this selector. >> >> Does this make sense? >> >> Cheers, >> Doru >> >> >>> Stef >>> >>> Just for the record, there are parts the world where you have to use your >>> GSM to browse the web. >>> Even in France there are parts of the world where you cannot access to >>> Youtube videos. >>> >>>> 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/ >>>> >>>> <Mail Attachment.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." >>> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "When people care, great things can happen." > -- www.tudorgirba.com www.feenk.com "We are all great at making mistakes."
