Having spent the better part of 2010 building PDF reports, I can say that I would like to see a complete overhaul of cfdocument. It’s time to bring the HTML and PDF support up to current standards. If I had to narrow it down to a few specifics, here we go:
- Whatever is currently limiting the HTML/CSS rendering needs to be updated or replaced.
- We need to have some better way to either calculate, force, or hint to the engine where we do and do not want page breaks.
- When I create a PDF form, I have the option of making a text field with a variable font size, so the text better fits into the field. I would love to do that inside a cfdocument.
I think that the updates to cfdocument, and with the addition of cfpdf, great strides have been made to bring enterprise features to ColdFusion’s pdf generation, but now it’s time to help the developers meeting the demands of smaller clients.
Update: So, uh, it’s been a long week. I want this in CF 10. 
This is long overdue and should really be in CF10. CF11 isn’t due until 2014.
Since Adobe is a member of WebKit community, and they have already embed WebKit web rendering engine into Dreamweaver, I think it is possible to do the same for ColdFusion. Currently, using cfhttp + cfdocument cannot generate a web thumbnail perfectly. I really like cfpresentation, so I think cfdocument should update its pace for better document generation.
File them here as Enhancement: http://cfbugs.adobe.com/cfbugreport/flexbugui/cfbugtracker/main.html
I build dynnamically generated PDF reports. After the end of the quarter the reports don’t change. It would be nice to cfcache PDFs.
cfdocument has an option to save the PDF to a file. You can probably just save the file to the hard drive, and check to see if it exists the next time someone tries to generate it. Don’t forget to make the file name unique to the report & quarter.