Attached is a patch and a tarball of new files to add example / test programs for pdf, ps, and svg surface types.
Created attachment 4471 [details] [review] patch for ChangeLog, configure.in, and examples/Makefile.am
Created attachment 4472 [details] New files for pdf, ps, and svg test programs Extract this tarball in the examples/ directory. I don't have CVS access yet, so I can't commit myself.
By the way, these are the examples that suffer from the issue described in http://lists.freedesktop.org/archives/cairo/2006-January/006191.html so they need some autotools work to get them to work right.
Committed. I have no build problems and the examples run. Are you doing an autogen.sh?
Really? odd. It builds fine for me, but doesn't run correctly. I am doing ./autogen.sh. Do the examples produce files that look reasonably like eachother (other than backend-specific differences) and like the file in the png example? Maybe there's an issue with my development environment. I'll look into it a bit more when I get home tonight. By the way, the ps and svg surface examples were copied from the PDF example, and I just noticed that the svg and ps surface examples contain the following lines near the end: std::cout << "You must compile cairo with PDF support for this example to work." << std::endl; These should be changed to SVG or PostScript instead of PDF. Sorry about that.
Yes, they run fine, apart from the PDF one, because I don't have PDF compiled into cairo. The images all looks the same. I fixed the messages. I'll do a new release soon, if that's OK.
It'd be nice to have an example for an XlibSurface and a Win32Surface (since I believe those are really the only surfaces officially supported by C cairo at the moment besides ImageSurface), but I'm not sure that I'll get around to them soon. Perhaps they could be borrowed and adapted from the C cairo examples (if they exist), but I don't think it's worth waiting for that for a release. I say go for it.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.