Agreed, GDI+ also is easier, its C++ just like KWQ, and it was designed for vector graphics afterall. My initial attempts (from long time ago.. pre open development WebKit, back when webcore-125.tar.gz is all i had to work with ;)) at porting KWQ to GDI+ was decent, but KWQRegion.cpp always gave me trouble, since it didn't correspond to GDI+ Region exactly and using Bezier Paths didn't work well either for some transformation stuff. I guess we can cross that bridge when we come to it? Initially, IntPoint, IntRect, etc.. in /platform would be a good place to go ahead and move to GDI+ on Windows since its mostly explicit casting to and fro stuff. On 1/16/06, David Hyatt <hyatt@apple.com> wrote:
On Jan 16, 2006, at 3:28 PM, Justin Haygood wrote:
On 1/16/06, David Hyatt <hyatt@apple.com> wrote:
On Jan 16, 2006, at 3:04 PM, Justin Haygood wrote:
We have several libraries we can choose from:
GDI GDI+
The concern with GDI+ is that it only works on XP/2003/Vista as well, right?
GDI+ is redistributable on older platforms (98/2000/ME).
Yeah, true.
Windows Presentation Foundation (XP/2003/Vista only)
I don't see this as an option.
Cairo (portable) - Mozilla's choice, LGPL'ed
Is Cairo built on GDI or GDI+? Will it work on Win2k?
I don't know. I believe GDI. Should, Both GDI & GDI+ work on Windows 2000.
In order to do some of the SVG features, I assume GDI+ will be
necessary though...
GDI+ is what Mozilla used to use. Cairo is used for SVG if you have Firefox 1.5.
I would guess that Cairo requires gdiplus.dll.
I think GDI+ is what we should go with initially. Cairo might be interesting as a way to do SVG eventually, but for now I think we should not define SVG_SUPPORT and basically not worry about SVG. The initial goal should be the bring-up of the HTML rendering portion (SVG can come much later), and I don't think Cairo really provides much of any benefit for that (although I'd be happy to be proven wrong).
dave