Hi guys, theyâre all great ideas - but I guess I should have added the caveat - âthat you can easily testâ. It sounds like maybe using class methods puts it closer to the simpler camp you are suggesting - and I would like to push the idea of using the debugger to create the missing method (a unique feature we can sing about). Weâre trying to help bridge a balance between unique and familiar, and to be honest the quicker we can move people to the harder problems the better. Itâs not clear to me if you can just invent new problems - but if so, we might hit you guys up for some more ideas. Tim Sent from my iPhone Sent from my iPhone
On 11 Jul 2018, at 21:43, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 11 Jul 2018, at 22:17, Hilaire <hilaire@drgeo.eu> wrote:
Le 11/07/2018 à 16:43, Tim Mackinnon a écrit :
I can see proâs/conâs either way - but wondering what others think.
IMHO, the simpler the better, particularly for users with no knowledge on Pharo.
Hello world could be class-less just: Transcript show: 'Hello world'
Hilaire
-- Dr. Geo http://drgeo.eu
Even shorter:
'Hello World!' crLog.
A variant using the Growl disappearing popup:
self inform: 'Hello World!'.
Using a dialog:
UIManager default alert: 'Hello World!'.
Using a window:
'Hello World!' asMorph openInWindow.
For real terminal output, there is this possibility:
Stdio stdout << 'Hello World!'; lf; flush.
All these are nice alternatives that can be used to explain different approaches/techniques, although they might be beyond what is expected.
Sven