[chromium-dev] Re: Is creating a custom PDF rendering backend a sound idea?
Here's the blog of the guy who seems to do the most work on the Windows+Cairo WebKit build: http://lwat.blogspot.com/ He occasionally posts status updates. On Mon, May 18, 2009 at 1:10 AM, Ben Harper wrote: > > Thanks for all the feedback. I think I'll give the plain WebKit + > Cairo > thing a go. > > On May 18, 3:06 am, Joel Stanley wrote: >> On Mon, May 18, 2009 at 05:46, Evan Martin wrote: >> > 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. >> >> Midori uses it. 'midori -shttp://path.to/website'will output a pdf >> of the site. >> >> http://www.twotoasts.de/index.php?/pages/midori_summary.html >> >> Joel > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Is creating a custom PDF rendering backend a sound idea?
Thanks for all the feedback. I think I'll give the plain WebKit + Cairo thing a go. On May 18, 3:06 am, Joel Stanley wrote: > On Mon, May 18, 2009 at 05:46, Evan Martin wrote: > > 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. > > Midori uses it. 'midori -shttp://path.to/website'will output a pdf > of the site. > > http://www.twotoasts.de/index.php?/pages/midori_summary.html > > Joel --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Is creating a custom PDF rendering backend a sound idea?
On Mon, May 18, 2009 at 05:46, Evan Martin wrote: > 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. Midori uses it. 'midori -s http://path.to/website' will output a pdf of the site. http://www.twotoasts.de/index.php?/pages/midori_summary.html Joel --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Is creating a custom PDF rendering backend a sound idea?
On Sun, May 17, 2009 at 2:53 PM, Ben Harper wrote: > 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 be blunt, if you can't get WebKit/Win to compile in days, I'm not sure you're prepared to author a PDF backend. Getting WebKit for Windows to compile is not difficult (I speak as someone who's done it over a dozen times, on various different machines, and has run into all the line ending mismatch/cygwin mismatch/svn mismatch/etc. problems you can have). 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? Depends on the backend. Nontrivial, not less than a month. PK --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Is creating a custom PDF rendering backend a sound idea?
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 wrote: > On Sun, May 17, 2009 at 4:27 AM, Ben Harper 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 -~--~~~~--~~--~--~---
[chromium-dev] Re: Is creating a custom PDF rendering backend a sound idea?
On Sun, May 17, 2009 at 4:27 AM, Ben Harper 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 -~--~~~~--~~--~--~---
[chromium-dev] Re: Is creating a custom PDF rendering backend a sound idea?
I think this would be out of scope for WebKit. Probably would fall under non-goals: http://webkit.org/projects/goals.html That said, I be this already works with the Apple WebKit Windows build. If you build WebKit with CG support on Windows then you likely already have this support from CG. :) You won't have any license to distribute CG, but it might work for your purposes if you don't need to distribute it. Otherwise maybe Skia or Cairo graphics libraries already support this. The Graphics layer (which is below WebKit) is the right place to add this support IMO, not WebKit itself. -eric On Sun, May 17, 2009 at 9:27 PM, Ben Harper wrote: > > Hi, > > 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? > * Is this a really bad idea, for some reason that I don't foresee? > > Thanks, > Ben > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
