On Sat, 27 Mar 2004, Bob Jamison wrote:
Bryce,
I was thinking, wouldn't it be nice if Inkscape had its own debug output console, like many apps have? This is almost unnecessary on Unix, but important on platforms that do not have pty-like consoles.
Not a bad idea.
How about adding a couple of methods to the Inkscape class (since all code pieces in Inkscape should have it as their parent), like inkscape->error("format", ...) and inkscape->warning("format", ...); .
Could we be certain that all of the places we'd want to emit errors would have visibility to the inkscape class definition? I.e., are there any sub-libraries that we'd want to emit debug info but not be tied too tightly to Inkscape? How would this work for Inkview?
We could use this to redirect the debug output to either the same Glib g_message() and g_error() output we have now, or to a separate Gui. A simple text console similar to Mozilla's Java Console would be excellent. We could redirect many types of informational messages to it. And it would be in a format that users could easily email to us in case of problems.
*Nod* Do you have examples of how other apps have done it, or do you think the Mozilla approach is completely representative?
Bryce