🚀 go-pugleaf

Patric Aalto writes:
>
>I am having big problems in coding the routines to handle these
>things, whereas the polygon filling etc. routines were just solutions to
>very well-defined problems, and therefore quite easy to do. I think this
>is what James Hague meant, and I must say I agree with him in this.

That's it exactly, with the emphasis on "well defined."  Line drawing,
texture mapping, 3-D perspective transformations, VGA registers, etc.,
are all subjects which you can walk over to your local college library
or bookstore and find out all sorts of information about.  Or you can
subscribe to various magazines (Dr. Dobb's, etc.) and get watered down
rehashes of the same thing, if you prefer.  With a book or few magazine
articles and a little experimentation, you're all set.

The difficult things are those related to YOUR game.  Some topics can
be generalized to apply in many situations, but you can't buy a book
explaining how to do EVERYTHING which makes your game what it is.
There are technical issues, play balance issues, asthetic issues,
philisophical issues, you name it.  These are all fuzzy areas which 
nobody but you can really answer.  Graphics routines, etc. are usually 
just the grunt work.  Games written by programmers at heart usually
aren't very good.

--
James Hague   
exuhag@exu.ericsson.se