🚀 go-pugleaf

> Before I get any more e-mail on this topic, I apologize for jumping the gun
> before I saw the code.  I haven't tried it yet, but I guess it's pretty obvious
> he does know what texture mapping is.  I would like somebody to explain, though,
> how his code resembles a simple line drawing algorithm.  I would also like to
> hear some comments on the limitations of this method.  

OK, I will post pseudo-code, but for now, a simple explanation:

First, the scaling code.  The Bresenham line drawing revisal was implemented
into the CreateScaleTable.  What happened here is the routine "draws" a line
from point A to point B.  Whenever the line would normally increment the Y
coordinate (this is for scaling down), a whole row or column was cut.  Scaling
up, it would total the number of pixels it could put on one Y row and store
it.  When the routine went down a Y row, the index was incremented and it
started on the next line of pixels.

The rest of the scaling code had nothing to do with Bresenham.  That is why
it is possible to create the tables in advance.

The perspective code added one more twist...this time an actual line (i.e.
calculated to determine the slope of the perspective).  This was done in
CreatePerspectiveTable...just a line drawing algorithm that was toned down.
That's all.  Without getting technical (yet), it would determine the number
of Y pixels down, subtract that from the new (requested) total height of 
the image twice (or times by two and subtract), and then create a Scale
Table for that row as described above.

Taht's all there is to the code.

Josh