That’s exactly the exploratory attitude we like to see... I think the code completer is pluggable and can be selected in the settings (I think there are 2, and their history is probably in this list somewhere), so you can try your own too.
Tim Sent from my iPhone Sent from my iPhone > On 26 May 2018, at 16:10, Andrzej Olszak <andrzej.ols...@gmail.com> wrote: > > Hi Tim and Nicole, > > Thanks for great tips. The click+keyModifier actions are extremely useful, > and combined with breakpoints make for a great way of 'peeking under the > hood' of the existing features. > > Also, I've just found a perfect piece of real code to do some learning and > experimenting on - it will be the code completion itself! ;-) > > Andrzej > >> On Fri, May 25, 2018 at 10:47 AM, Nicole de Graaf <n...@soops.nl> wrote: >> Hi Andrzej, >> >> my way of doing it: >> >> Searching in the image what other guys are doing. >> >> Finder: asMorph >> >> and here you can find methods like >> >> #openAsMorph .. you can get a clue. >> >> or: >> >> ‘some text’ asMorph inspect .. >> than you get the object and you can search the class and from here the class >> the references. >> >> All my steps are based on code reading not code completion. >> >> Code completion I use more if I know what is should be and use the same >> method names as the other developers. >> >> Nic >> >> >>> On 25 May 2018, at 03:12, andreo <andrzej.ols...@gmail.com> wrote: >>> >>> Dear Pharoers, >>> >>> I'm just starting out with Pharo 6.1, and I'm trying to use code completion >>> to interactively explore various objects and their messages. However, I'm >>> having difficulties doing this efficiently - I think I must be missing >>> something obvious, and I hope you can point me in the right direction. >>> >>> For instance, let's say I have the below in Playground: >>> >>> 'some text' asMorph >>> >>> and I would like to display the morph object as a window, but I don't know >>> the exact message name, or whether such a message exists at all. If I type >>> "Window", then the completion popup will show a long list of matching >>> messages, but won't show their documentation or argument names, so it will >>> be difficult to know exactly what these messages do. >>> I can see that one can do "Do it and go" on an expression and then browse >>> the available messages in Meta, but maybe there is simpler/faster way? >>> >>> How would an experienced Pharo user typically go about discovering the right >>> messages in such situations? >>> >>> Best regards, >>> Andrzej >>> >>> >>> >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >
