I've been trying to figure out what plans are afoot for GnomePrint. After a whole lot of research, it looks like the plan is to replace the current API with a pango-enabled Cairo API.
Unfortunately, this places me in a bit of bind. It sure looks like the best way to future-proof my application is to use PyCairo to generate a PDF file, and use the GnomePrint set_file API for printing and print preview (this is what Evince is doing). However, this API appears to be disabled in python-gnome-extras. I haven;t been following CVS HEAD lately; can anyone confirm if this is still the plan? Assuming it is, is there any reason to withhold the set_file API? It may be marked unstable, but at this point it looks like the entire GnomePrint API is going to be deprecated anyway, so having it will just make our lives a little easier during the transition.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
