[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Gratifying response
I'm glad to see my snivelling got others to post, and especially
glad that the posts weren't all, "Shut up, Doug!" ones. I think
your most important task right now is to define your program--the
scope of the background, the problem(s) to be posed to the user, the
user's objectives, etc. Once you have that framework set up, you
can start filling in the pieces with storyline. After the storyline
is fairly firm we can start worrying about graphics, animation,
sound, user interfaces, and the like. Some of those choices may
cause modifications to the story for technical reasons, but don't
concern yourself with that just now.
Keep in the back of your minds that we want to do this in a way that
allows for other data sets, i.e., we should be able to easily build
"Where in the Solar System...", "Where in the Seven Seas...", etc.,
on the same engine/data interpreter we develop for "Where in
Hell...". But only in the back of your minds; don't let it cramp
your style.
--
Doug Loss Even if you're on the right track,
Data Network Coordinator you'll get run over if you just
Bloomsburg University sit there.
dloss@bloomu.edu Will Rogers