That’s right. Just because I can’t be arsed to update this development blog it doesn’t mean I have stopped development. Quite the opposite: I have good news for all the ladies who get aroused by reading my code (there must be thousands of these) and for the standard geeks who enjoy reading progress updates.
The vector renderer is rendering -which is a nice thing for a renderer to do-, and it’s doing so a few days before the proposed deadline. The first Coding Period begins in about one week, and so does my exams period. Fortunately, with this “small” head-start I will be able to focus on my exams and still meet all the other deadlines; the vector renderer is one of the key pillars of my project (and quite a bit of work), so having it finished before the actual coding begins is a good thing.
So, what’s exactly done in the Vector Renderer? Well, pretty much everything important. The API is designed and in place, and pixels are being drawn on the overlay. Obviously, next week I’ll notice the renderer is missing some key features and a rehaul will be in order, but meanwhile I plan to write a blog post explaining the design and extendability of the class, which hopefully will also serve as a strong base for the API documentation that will go on the ScummVM wiki when the design is finished. I don’t really need to say that the whole class design gives me a raging hardon; you’ll find that out soon enough.
Until then, I’ll leave you with the moment you all have been waiting for: TEH PICTARS!!
…Actually, there’s just one picture comparing the standard Vector Renderer implementation and the AA renderer for fast platforms. See it after the jump, and click it to enlarge it. Or just draw your eyes closer to the screen.
(Editor’s notice: unfortunately, the image that was included here is lost and not available on archive.org)