I just checked in code that enables a feedback window to pop up when something is written to stdout or stderr (for example exception happened). The code collects various pieces of system and Chandler information, and optionally the user can add their own comments (and remove some of the collected system information) before submitting the information to OSAF with a click of a button.
If you don't want to see that dialog (for example, if you have test print statements scattered in your code), add --stderr argument when starting Chandler. This is the first cut of this feature so there are lots of possible ways to improve this. You might want to post your ideas to design list... -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
