"all Gung-Ho" (inevitably) for creating little 2D games they can show to their friends,
but they all seem to have a problem understanding this sort of stuff:
Code: Select all
move img "scaryMonster" from 60,75 to 400,500
and they have very great difficulty visualising a screen (or LiveCode stack) as something chopped up into squares (i.e. pixels).
Until children get to about 11-13 they are still in what Piaget termed the 'concrete operational stage', and while they can play chess
with pieces on a board they are unable to visualise a chessboard inside their heads and imagine moves of pieces on that board.
[Frankly, having stated that, I can cheerfully say that at 58 I still find that a bit hard.]
"Normally" (i.e. when I am teaching programming in a physical classroom) I explain this by using a 20 x 20 grid I printed out on
some paper and ran through my laminating machine, or mess around with a Canadian checkers board.
- -
Thinking about my upcoming online programming classes I really didn't feel very good about faffing around with a webcam
getting things badly wrong on the kitchen table.
So I ran up this fairly simplistic LiveCode stack which should serve in the same sort of way to my monster chess boards:
- -
What it DOES do is report the grid position of any of the octagons when they are dragged onto a square on the board.
What it DOESN'T do is tell you how to keep "little twonkums" focused while you're explaining the thing.
Stack removed as improved version made available lower down.