> > Message: 1 > From: Mariano Martinez Peck <[email protected]> > > Hi Benjamin. Thanks a lot for all the work you are doing. When we start to > build PharoDev 1.2 I would like to include your new recent submission and > this method finder. >
Thank you, it's a good news to hear :) > It is very good idea to merge both, as it was very confusing. > > Here is my feedback > > 1) You have to provide a help text somewhere. Ok, entering a message name > is > easy. For example, if I want to see all messages like #setUp for example. > That's intuitive. But, if I want to search the method that sending to an > object 'aaa' answers me 'AAA', it is not intuitive to type: 'aaa' . 'AAA' . > so....this should be explained somewhere. Maybe you can add a text > explaining this (like it was in the previous tool) in the code panel. > Because when you first open MethodName, the code panel is empy...you can > use > is and write there the text. Of course, an extra button help would be nice > too :) > Now, instead of having an empty text area, the method finder help is diplayed. About the button, I have no idea where to add it in the UI (it's already quite full) > > 2) In addition to 1) writing a HelpSystem chapter / Pharo Collaborative > book > is important. What I mean is that if we are going to include a new tool in > the Pharo mainstream, then it should be easy to use and documented. > I'm agree to try writing one, but I need further informations (and probably some help ) :) > > 3) The scroll of "change search envirorment" is veryyyyyyy slow. I know it > is not "your" fault, but maybe someone can give you an idea of how to > improve this. Maybe Tudor, Alexandre, Lukas, Gary...I don't know. > I've forgotten to initialize a class variable in PackageChooserUI. Now the default behavior is to show only packages. This way, the chooser is quick enough. I worked on a Package->Classes representation but it's slow and I had some trouble with selection so i've choosen to wait until packages be Objects instead of String to resume this part. 4) Most of the buttons are confusing because you don't know when you should > be able to use them. For example, all the button (browse, senders, etc) are > only usable when you select a specific implementor. But > > a) they are not disable at the beginning (before choosing a selector), thus > someone would try to use them just after selecting a method name. > > b) not all of them require an implementor. For example, to search the > senders, I don't need to select a particular implementor. Just having the > selector is enough. > > So...I would put those buttons inside the right panel (where you list the > implementors) or disable (grey) them when not needed. > It's fixed now :) > > 5) This one is difficult to explain....Take method name and type in the > serach inpit: 'aaa' . 'AAA'. Hit serach and you will see 'aaa' asUppercase > -> 'AAA' listed in the left panel. If you click EVERYWHERE inside that > panel, the first one is selected. Thus, it is easy and fast becasue you > DONT > need to go the the first raw and mark it. Ok? > > Now....do the same but write "setUp". You will see several methods that > match that. Select any of them, and in the right panel you will have a > list. > A lot of times, there is one implementor. And of course you want > that....but > doing the same of the previous case doesn't work. You have to go exactly to > that raw in order to select it. > > okok...I know, I am lazy :) > I'm pretty lazy too so now, if it's possible, the first choice isautomaticallychoosen ^^ Moreover, when a Method Name window is open, the focus is already given to the searching text area :) > > Thanks again for this > > Mariano > Thank you for your advice ^^ ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Message: 2 > > > Hi Benjamin. Thanks a lot for all the work you are doing. When we start > to build PharoDev 1.2 I would like to include your new recent submission and > this method finder. > > > I want to integrate recentMessage to replace the default one. > Same for the new Finder once it is ready. > I did not have the time. > I think that this is important to take the time to rethink what we want. > > Stef > Thank you :) Ben
_______________________________________________ Pharo-users mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
