âsimondenierâ wrote:
Read the comments if there are some, especially with snippets of code for do-it. Read the tests, try to find how one instantiate a particular object, then put a self halt in a test or create a new object in a workspace and open an inspector on it; interact with the object to send it messages and see how it reacts (with the class browser by the side of course).
Learn the strengths and weaknesses of the various browsers, and especially the shortcuts to quickly launch them (select some text in the source then): alt+b -> browse class alt+m -> browse implementors (method definitions) alt+n -> senders (messages calls) alt+shit+r -> references to class etc.
So basically yes. Understanding a Smalltalk program is somehow a heuristic process (like all program understanding): browse code, browse implementors or senders until you can not get further or lost track, make hypothesis about how it works and check by browsing again and querying live instances.
In Smalltalk the language and its syntax are simple, so you get more work to learn the whole API and the tools, especially since they are a bit unconventional. So I can understand that you feel lost. But the best way would be to learn by doing, with somebody while pair-programming.
Thank you for the hints and encouragement. My problems are probably not Smalltalk/Pharo specific - i might reveal that i have no formal training in programming or computer science. I did little things in Objective-C/XCode and Java/Eclipse and i really love the Smalltalk/Pharo,Cuis,Squeak experience compared to that. As i was not trained in other things, Pharo does not at all feel âunconventionalâ to me. Helene. -- View this message in context: http://forum.world.st/Screencast-proposition-Watch-someone-read-code-tp32448... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.