On 2/28/07, Uwe Grauer <[EMAIL PROTECTED]> wrote: > Ed Leafe wrote: > > On Feb 27, 2007, at 9:19 PM, Michael Hipp wrote: > > > >>> This is still uncharted territory, mainly because nobody has looked > >>> into it yet. I suppose we would take what wxPython uses and perhaps > >>> clean it up a bit, but until then, you still have the full wxPython > >>> printing mechanism available to you. > >> Unfortunately I find the wx printing framework to be a bit like > >> programming in > >> assembler. It is a "low level" tool shall we say. ReportLab has > >> spoiled me. > >> > >> At present I'm having pretty good success using ReportLab with > >> Ghostscript to > >> to print the resulting PDF. But Ghostscript seems a bit rickety at > >> times. > > > > Do you have ideas about a better way to approach this? If anything, > > Dabo is about finding that 'better way'. > > > > -- Ed Leafe > > Maybe at one point in time we could support printing with the help of > OpenOffice. > There is UNO (Python-UNO bridge): > http://udk.openoffice.org/ > http://udk.openoffice.org/python/python-bridge.html > > But i don't think that it is the right time for this now.
Is it really that bad that we don't support printing? We support PDF, various image formats, html, xml, and various text file formats for export already. It takes about the same amount of time to export one of those, open it up in a reader, and print it as it will to format and print it directly from the Dabo app. My opinion, but I don't see the need since we can generate files that look professional and can be printed from a host of reader apps. My $.02 > > Uwe > > _______________________________________________ > Post Messages to: [email protected] > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
