Issue 3722 in pharo: The Finder tool's help screen is poorly written and has bad grammar

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 3722 in pharo: The Finder tool's help screen is poorly written and has bad grammar

pharo
Status: New
Owner: ----

New issue 3722 by [hidden email]: The Finder tool's help screen is  
poorly written and has bad grammar
http://code.google.com/p/pharo/issues/detail?id=3722

1) why does it use "Selectors" instead of "Methods"? What is a Selector?
2) class's names -> classes
3) all the method's sources -> the source code
4) "your research use"  -> your research uses
5) "in this 4 modes" -> in these four modes

=====below: the current text====
The Finder can be used in 4 different ways:
        - Selectors: your research is done among selectors
        - Classes : your research is done among class's names
        - Source : your research is done among all the method's sources
        - Examples : your research use the Method Finder behavior
                           (for further informations, print 'FinderUI methodFinderExplanation')
                       
In this 4 modes, you can also tick the 'Use RegEx' checkbox.
If you pick this box, your search will be done using regular expressions  
instead of just matching.

The 'Select classes' button opened a dialog window  to select which classes  
will be used for the search.
The 'All classes' button is used to reset the classes selection.



Reply | Threaded
Open this post in threaded view
|

Re: Issue 3722 in pharo: The Finder tool's help screen is poorly written and has bad grammar

pharo
Updates:
        Status: Fixed

Comment #1 on issue 3722 by [hidden email]: The Finder tool's help  
screen is poorly written and has bad grammar
http://code.google.com/p/pharo/issues/detail?id=3722

A method is a entity (a CompiledMethod instance) representing a method,  
while a selector represents the name of the method (it's an instance of  
Symbol).

If you use the term "Method" some people will expect the search to be done  
in the source code of the method when others will expect the search to be  
done using the method's name.


And you know, such a title is not really pleasant to read ...

Attachments:
        Issue3722.1.cs  900 bytes


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3722 in pharo: The Finder tool's help screen is poorly written and has bad grammar

pharo

Comment #2 on issue 3722 by [hidden email]: The Finder tool's help  
screen is poorly written and has bad grammar
http://code.google.com/p/pharo/issues/detail?id=3722

Apologies for the title of the issue.  I realize you've put a lot of work  
into this tool.

As to Selectors vs. Methods:

If I open a "Method Finder" and type in "copy" I get the same
results as I get if I open a "Finder",type in "copy" and choose
"Selectors".

"Each method has a name, called its selector," Pharo by Example, p. 80.

IMHO Methods is more immediately recognizable and won't confuse
anyone.



Reply | Threaded
Open this post in threaded view
|

Re: Issue 3722 in pharo: The Finder tool's help screen is poorly written and has bad grammar

pharo
Updates:
        Status: Duplicate
        Mergedinto: 3743

Comment #3 on issue 3722 by [hidden email]: The Finder tool's help  
screen is poorly written and has bad grammar
http://code.google.com/p/pharo/issues/detail?id=3722

Can you provide *one* merged Finder version that is ready to merge into 1.3?