7 ms·
The first time I heard about this approach was Boxer: http://edutechwiki.unige.ch/en/Boxer http://edutechwiki.unige.ch/en/Boxer Some more info here: http://lam
by ianbicking 11y ago
The first time I heard about this approach was Boxer: http://edutechwiki.unige.ch/en/Boxer http://edutechwiki.unige.ch/en/Boxer
Some more info here: http://lambda-the-ultimate.org/node/4695 http://lambda-the-ultimate.org/node/4695
Paper with some screenshots: http://www.soe.berkeley.edu/boxer/20reasons.pdf http://www.soe.berkeley.edu/boxer/20reasons.pdf
And another more contemporary document: http://www.pyxisystems.com/file/BoxerStructures.pdf http://www.pyxisystems.com/file/BoxerStructures.pdf
It goes beyond framing a bit, making things like variables concrete (they are actual boxes that contain a value). But it doesn't do full Scratch-style pluggable programming, the statements are still text, as in "Frame-Based Editing".
- abecedarius 11y agoYes, and the remark at the post's bottom, "Structured editing wasn't actually a bad idea, it was just poorly executed." seems oblivious to Boxer -- I found it usable enough (and inspiring). diSessa's book http://www.amazon.com/Changing-Minds-Computers-Learning-Literacy/dp/0262541327 http://www.amazon.com/Changing-Minds-Computers-Learning-Lite... has more on the philosophy and the experience with kids using it. The writing style's a bit of a slog.