On Sat, Oct 28, 2006 at 03:26:35PM -0400, MenTaLguY wrote:
On Fri, 2006-10-27 at 13:16 -0700, Bryce Harrington wrote:
If we do this (and I agree it makes sense), then we must have a plan on how to do it, and someone to be point person on the effort for making the decisions. If someone can identify these two things, then we can make this a hard block on the release.
Well, since Alexandre hasn't expressed interest in heading this up, I guess I'll do it. It's a pretty bad situation to begin with, but after all those Slashdot posts, it's also a question of personal honor for me.
So, first step. Compile that feature matrix. I'll prep a spreadsheet.
I went back through this thread for todo items. Most of these are from Miklos' initial email, so perhaps he has additional suggestions for what needs done...?
* Identify feature differences between the three PDF implementations
* Cairo-based PDF renderer - Add optimizations like creating surfaces with only the needed bbox size, rather than the full size of the output - objectBoundingBox clipping doesn't work... need to find out why - Cairo-PDF patches are not yet finished. These will need to be incorporated into Cairo. - Text is quite unstable (isn't being shown except in 'root' layer) - Images are unstable - Masking is supported only with constant alpha * Ensure blur works with export to pdf via rasterizing of blurred objects in a fixed resolution
Any other things?
Could someone suggest ways to test everything that'll need to be supported?
It sort of sounds like while it would be nice to use Cairo+GeGL for blur support, since GeGL hasn't had a formal release and hasn't identified a stable API yet, that could be a challenge. Besides, if PDF doesn't support effects and we have to rasterize such things anyway, it may as well be done internally for now.
Bryce