On Wed, 28 Feb 2007, Michael Hipp wrote: > ReportLab produces PDF files. Nothing more or less. I've discussed the > printing issue on the ReportLab mailing list at some length. (Too much > length actually, as I probably offended some people -- I just couldn't > believe it was so difficult to actually just print a PDF.) The available > answers came down to: a) make do with GhostScript, b) buy a commercial > solution. They "officially" consider the printing question to be OT. Once > the PDF file is on disk, they're done.
Michael, Later today I'm getting back to adding printing capability to our approximate reasoning model. I'm trying to use the Dabo ReportDesigner and reportWriter to feed it to ReportLab. My plan is to use the wxPthon print dialogs to select whether to print to file, printer, or screen (as well as setting up options within each destination). When the report is to go directoy to the printer (without passing Go, collecting $200, or displaying in xpdf/acroread), the output will be sent directly to lpr. Of course, one can view the report on screen, then send it to the printer. The acroread/xpdf output can be redirected to /dev/nul. I learned a long time ago that, at least with CUPS, one can type 'lpr somefile.pdf' at a console (without X running) and out it comes from the printer. > The above isn't meant to be critical of ReportLab. It's terrific and the > authors are very helpful. The problem really is Adobe's bloated, pretentious, > unbearable Reader app. There are alternatives. My default is xpdf. Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
