What about a fast search box on the right hand side of the menubar:)
Something that kept an index for snappiness a la Spotlight on the Mac.
I think ideally you would type in arbitrary text, and if you type a
class name you'd get that as the top hit, if you type a #selector:
then you might get a list of classes that implement it, etc. But
here's an even more radical idea: What if you could just type in a few
interesting keywords and get back hits in the class comments too?
There's a lot of "stuff" in a Squeak image. We might break a little
ground if we thought about finding stuff in the image in terms of
document retrieval.
On Sun, Dec 6, 2009 at 10:15 AM, Eliot Miranda <
[hidden email]> wrote:
>
>
> On Sat, Dec 5, 2009 at 5:33 PM, K. K. Subramaniam <
[hidden email]> wrote:
>>
>> On Sunday 06 December 2009 03:11:31 am Jerome Peace wrote:
>> > Why is that so?
>> Protocol? basic vocabulary? A method name does set an expectation and
>> people
>> build up a working vocabulary over time. My early frustrations with
>> Squeak
>> :-( were with statements like:
>>
>> Morph new name
>> SmalltalkImage explain
>> PolygonMorph new edit
>>
>> asBit breaks the protocol of using asInteger to map an object to a number,
>> so
>> it is not discoverable manually through Message Finder or automatically
>> using
>> Method Finder.
>>
>
> +1
>
>>
>> > Does anything need to be done about it?
>> > What would help reduce the confusion/ignorance?
>> Yes. Message name finder could support wildcard searches (e.g. "open",
>> "open*",
>> "*with*"). It could present results sorted by relevance (say, number of
>> senders + number of implementors) to encourage vocabulary.
>>
>> Subbu
>>
>
>
>
>
>
--
Ron
Locked
