Dave — Thanks for your input.
Dave Sawyer wrote:
Most people gain little useful information from a crash report and including one by default just make it difficult for people to read about your problem.
Agreed. But whether the thread is difficult to read depends on
how the crash report is posted — which was the point of my post.
Dave Sawyer wrote:
If someone asks you to post a crash report...
I think a potential respondent is more likely to take an interest in the problem if the crash report is
already supplied via a link that doesn't make the thread difficult to read.
Dave Sawyer wrote:
...then we just deal with the formatting issue.
Rather then merely tolerating the "formatting issue" of lengthy inline crash reports, I was hoping readers or
Discussions staff could come up with some practical alternatives.
The following idea of mine is practical for me, but others probably wouldn't want to bother setting up a free, web-based
Posterous blog just to post their crash report. ...But once the blog is set up, a PDF of the crash report can easily be created in
TextEdit and that PDF emailed as an attachment to post@yourblogname.posterous.com — which then automatically creates a blog entry consisting of a slick PDF viewer. So with a hyperlinked thumbnail, I can post future crash reports like this...
Click below for the crash report:
...Perhaps
Discussions staff could recommend a way to link to crash reports — for members it makes threads faster to load & easier to read and for Apple it reduces server space & bandwidth usage.