questions about the PS backend

Hi Steve,

    >> 7) The template backend uses=20
    >>
    >> verbose.report('Error: %s'%msg)
    >>
    >> Should this be 'verbose.report_error' instead?

Yes.

    > No verbose() at all! But I agree I think it should be
    > 'verbose.report_error'

Yes, it should. All printing should either go to verbose.report or
verbose.report_error, so that the user specified output handles are
used. This was just an oversight in backend_bases.error_msg.
Everyone should feel free to fix these as they find them.

Of course, GUI backends are an exception, where the error messages go
to the dialog box, as you noted.

    >> Also, there is a new PS backend now. I've been working on
    >> backend_cairo.py and today got it producing its own png and PS
    >> files.

Great - there have been a number of people who've been interested in a
cairo backend since the earliest days. When you get the thing so that
you're happy with it, you might want to search for cairo on the
mailing list and let these people know there is one.

Thanks!
JDH

Hello,

···

On Sun, Oct 31, 2004 at 10:33:27AM -0600, John Hunter wrote:

    >> 7) The template backend uses=20
    >>
    >> verbose.report('Error: %s'%msg)
    >>
    >> Should this be 'verbose.report_error' instead?

Yes.

    > No verbose() at all! But I agree I think it should be
    > 'verbose.report_error'

Yes, it should. All printing should either go to verbose.report or
verbose.report_error, so that the user specified output handles are
used. This was just an oversight in backend_bases.error_msg.
Everyone should feel free to fix these as they find them.

Then the recent change to error_msg_template should be reverted,
shouldn't it?

All the best,
Jochen
--
http://seehuhn.de/