Hmmm... yes I'm aware of the Cairo thing. I just gave up on trying to build Webkit on my Windows machine, because I can't stand spending days just to get something to compile, when someone else on my team is waiting for my proof of concept.
To the guys who ported Webkit to Skia, my question is this: Is porting Webkit to yet another backend 1 week, 1 month, 1 year? Thanks, Ben On May 17, 10:16 pm, Evan Martin <e...@chromium.org> wrote: > On Sun, May 17, 2009 at 4:27 AM, Ben Harper <rogo...@gmail.com> wrote: > > Before I get going, I just want to make sure that I'm not reinventing > > the wheel, nor wasting my time. I know that on OSX, CoreGraphics can > > output to PDF, but I need this functionality on Windows. > > I've got a C++ PDF authoring library which I'm going to strap on as a > > rendering backend. This kind of thing could really just go into > > WebKit, but I gave up on that because building Chrome on Windows is > > just so much easier. Of course, the code will logically fit into the > > WebKit tree, so I can't see it being a problem moving it back upstream > > at some point. > > > Anyway, my questions are: > > * Is anybody already doing this? > > WebKit (but not the Chromium port) already targets Cairo via GTK, and > Cairo supports PDF output. I'm not sure anyone's using it for PDF > output yet though. > > > * Is this a really bad idea, for some reason that I don't foresee? > > http://www.ietf.org/ietf/IPR/adobe-ipr-draft-zilles-pdf.txt --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
