dank at kegel.com
Fri Mar 9 15:46:15 CST 2007
>>>> Since Mono has implemented much of gdiplus already
>>>> ( http://www.mono-project.com/Libgdiplus ),
>>>> we ought to be able to just slurp that into Wine and
>>>> get quite a ways.
>>>Except that's based on top of Cairo, whereas ours should be based on
>> But cairo has a win32 backend. So I think we can use mono-libgdiplus.
>Even if we wanted to do it that way, it wouldn't work; gdiplus exposes
>gdi32 handles, so we'd somehow have to get these through Cairo.
Well, I heard libgdiplus already has a bundled version of Cairo,
we could replace that with a win32-cairo, then hack it
up to let the gdi32 handles shine through, maybe...
(For those looking for a pointer to cairo-win32, see
Maybe we could start by just getting it building?)
Whether or not gdiplus is in scope for wine is really a function
of whether it's practical to implement, and whether doing
so would solve important problems for us. Maybe it would
help to list the problems we have with using native gdiplus.
I think it's just two: some apps don't bundle it, and it might be slow.
The speed problem might be solvable by doing a DIB engine instead,
as Dmitry implied.
So Huw, you sounded like you thought doing our own gdiplus was
a good idea. How strongly do you feel about it?
Think I should have somebody try to tackle a DIB engine instead?
Wine for Windows ISVs: http://kegel.com/wine/isv
More information about the wine-devel