wantedman's Journal: SK2 Tile Engine Progressing

I thought I'd work on SK2 for two hours then work on my Thesis for the rest of the day.

I was thinking about creating a structure like this:
CGraphics
  - CTileEngine
  - CSprite

But I decided that I was over-engineering the problem, so I went with
CTileEngine
- CSprite

Where CSprite access CTileEngine through a friend function. It'll speed things up a bit. It means I can't simply drop in a new CTileEngine if I switched engines on my next project, says, to a vector based engine, but it'll be much speedier on this project. :D

Basically, it works exactly like my font library. It loads everything up and then it spits out each word until you need a state change, which it renders everything, changes the state and continues until we run out of data, which it flushes everything out.

Hopefully, my engine will rock. It's taken too damn long to make...