L
Luc The Perverse
zero said:Actually I think interaction is a lot more important than visually
appealing features. Most visual stuff is, certainly in the early stages,
going to be disappointing imo. However, if they can interact with
programs
they made themselves, they'll find it more interesting. They will want to
make changes to the code and see how that affects the interaction. At
least that's what I found interesting. I could never see an example or
exercise without wanting to "improve" it.
For example I believe a program showing a static picture and playing a
sound file less appealing - and a lot harder to make - than a text-only
"guess the number" game. So interactivity is the key. And of course
games
are interactive, but they shouldn't be presented as "computer games",
because that brings up visions of Doom and The Sims.
Perhaps you are right.
But there is a stigma attached to programs that run in the console window.
But it doesn't have to be one way or the other. The user interaction could
already be coded by the professor, and the students need only write the
interactive part. The coding part for the students would be approximately
the same difficulty, and may even be easier if the interaction function is
Play
But on the other hand - the instructor could provide a "guess the number
interface", and only require the students to provide the code which allows
them to make it run on the same order of complexity as if they had written a
text based game.