> Uli: We also still need someone to implement the screen display routines. That
> is, drawing of objects onscreen in a fast way and with correct overlapping.
> This could also be started on Windows if the authors create wrappers around
> Windows data structures and API calls. That means the authors will have to
> create some classes that enclose and hide any drawing calls and map them to
> the appropriate Windows calls. Another part of the code should only call
> these wrappers and be completely platform-independent and perform the
> actual drawing operations (i.e. drawing a roundRect and a shadowed button
> overlapping correctly...).
Adrian: Of course, the wrapper classes need to accept a standard calling
method! :) We need to decide what calls are needed and what the syntax
should be for them before anyone starts on creating these classes. Although
the calling syntax should be fairly easy to change later, best to get it
right the first time.
