Well, this is all I have to show right now. I'm going back and sprucing up the logging and such.

The above example is totally controlled by this style sheet. Even the parameters inside the <> and the values inside of the "". I figure this way anybody can modify the style so that its easier to read and spot stuff. This is my preferred style. Some people might not be able to see the flashing '!', to those people I say sucks to be you :P. Internet Explorer doesn't support the before and after tags, so thats why you can't see them (*cough*get firefox*cough*.)

Edit:
The logger is used like so:

dft::LogDebugOutput(FormattedTextString, OutputType, ...);

The output type can be any number. The library defines dft::DOT_TEXT = 0, dft::DOT_WARNING = 1, dft::DOT_ERROR), but you can supply your own and then add a corresponding OUTPUTTYPE# class in the style sheet. So, say you have a client/server system setup:

enum ENGINE_DEBUGOUTPUTTYPE{    DOT_CLIENT_TEXT = 0,    DOT_CLIENT_WARNING = 1,    DOT_CLIENT_ERROR = 2,    DOT_SERVER_TEXT = 3,    DOT_SERVER_WARNING = 4,    DOT_SERVER_ERROR = 5,};//  Now you would needfont.OUTPUTTYPE0{	color:				rgb(255, 200, 200);	font-size:			12px;}font.OUTPUTTYPE1{	color:				rgb(255, 255, 0);	font-size:			12px;}font.OUTPUTTYPE2{	color:				rgb(255, 0, 0);	font-size:			12px;}//...font.OUTPUTTYPE5{	color:				rgb(255, 0, 0);	font-size:			12px;}

This way you could separate client messages from server messages. I find it makes things a lot easier [grin].

Edit 2: As a side note, it feels really good to be able to add a whole list of objectives to the finished pile in under 10 minutes (dftInput.) Audio should go the same way, since none of my code needs to change in that module.