GDI architecture

[Jacek Bator]

Hello

I'm tring to understand current wine gdi architecture, and as far as I 
see its strictly based on and mixed with XWindows. Is it inheritance of 
early development. Does any one tried ever to rewrite this layer not 
only to separate dll, but to implement real drivers for graphics
rendering.
I mean not only  connected with core gdi in source but during runtime. 
With that kind of implementation there would be much easier to implement 
new backends for graphics ... not only X11 but also on other graphics 
systems (framebuffers, other systems like beos,atheos). I know that this 
is big stuff but it gives lots of advantages. Such system sould 
implement all rendering (text, lines, etc.) in software (aka GDI engine 
or HEL on Windows) which largely done in wine already, and if driver 
makes avaluable any methods with other capabilites than raw framebuffer 
use them.
When I've look on aplications with well designed plugins systems,
I see that this effort was worth of costs for implementiation.

I would like to know if it was discusion about that previously. And what 
you are thinking about this.

Jacek Bator

jbator at man.poznan.pl