[Alephmodular-devel] Status of Drawing Abstraction

[Br'fin <br...@ma...>]

Well, with the tweaks to the last couple of things, I believe that I've 
almost completed the base requirements of the Drawing Abstraction. Now 
there's a couple things I'd like to get done before I try and merge 
this all into the main trunk.

One is a matter of documentation. I need to reflect the current 
structure into the design documents for the abstraction. So much of the 
more recent stuff just sort of came together in one way or another and 
I need to note it more clearly.

The other issue is one of eyes. People willing to browse through the 
marathon2/Display directory and note things in the API or general C/C++ 
structure of things that are questionable. Or to question how certain 
elements were implemented in terms of CDisplay is welcome as well.

I'm a little worried about the dependancy of various headers. And I 
have no idea how to properly separate them out, or arrange them for 
efficiency. It was just my impression that changing some files should 
not require recompiling preferences.cpp.

Should there be a specific set of headers necessary? As in you need to 
include CDisplay to use that and then CBuffer and CDContext if you want 
to work with the buffer and then use its drawing commands. Or should it 
be a single master include that basically grabs the includer everything 
there is to access the entirely of the drawing abstraction?

-Jeremy Parsons