> Patrik Stridvall wrote:
>
> >Another "library" you should look at is Microwindows
> >(http://www.microwindows.org) which under MPL (optionally
> GPL).
>
> >Personally I think that in the long run we are better off
> >having a CPU-only rendering engine of our own. However in
> >the meantime by all means use a library. GPL:ed or not.
>
> it would be pretty difficult writing something as fast and
> small as the
> microwindows library. there seem to be a lot of people
> working on this thing.
> if possible, why not use it?
Microwindows doesn't really have the same design philosophy
as Wine. I have discussed that personally with Greg Haerr
(the main author) of Microwindows some year(s) ago.
See the mailing-list archives.
Microwindows aim towards embedded systems so it rendering engine
aims to be small and fast. Wine's rendering engine should IMHO
aim to be flexible and fast.
By flexibillity I mean that Wine's rendering engine
should use the underlying driver, like the X11 driver,
if it can do the rendering faster. Note that it often
can since the driver can directly or indirectly access
the underlying hardware.
Also whether Wine's rendering is small or not almost
totally unimportant as long it flexible and fast.
Not so for Microwindows.
That said I haven't look at Microwindows for over a year
but judging from my discussions with Greg Haerr I doubt
this has changed very much.
But by all means link with or borrow whatever you can
from Microwindows in the mean time. Just clearly mark
it in the code we the can fix it later. Perhaps we
persuade Greg Haerr to relicense the things we will
borrow.
