Maybe the core of the suggestion is start with the Playground and
then go to the code browser, that's my workflow coming from other
languages like Python and Scheme, and having the playground to
emulate REPL before going to code browser has been really
refreshing and also "going from scripting to object" is a well
received approach in our Data Weeks.
So the Pharo Quick Start, after providing the installation instrucctions could be something like:
"""I'm not sure what you mean by *PrintIt:*. If you mean type 'Hello World' in the Playground and just *Print it*, that's not really a "program." Sean P. DeNigris wrotehernanmd wroteTo me the Hello World in Smalltalk was always just writing: 'Hello world'+1. While putting it in a class shows a few more of the system's features, it also makes it seem more complex than other languages, when that's not really true. Why not just PrintIt: 'Hello world'? If it seems important to show classes, maybe start with PrintIt: 'Hello world' and step-by-step build through `Transcript show: 'Hello world'` to the class-based solution. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html-- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html