rename #possibleCauses to #seasidePossibleCauses ?

[GoogleCodeExporter]

since we're adding the method to Exception should we namespace it?

Also, we might consider adding #seasideDescription to provide a few
sentences describing what the exception means in plain language. Would be
user friendly for users while developing.

Original issue reported on code.google.com by [email protected] on 17 Jan 2009 at 11:27

[GoogleCodeExporter]

Instead of #possibleCauses or #seasidePossibleCauses we could also just 
implement #renderOn:, would maybe 
make more sense and it could possibly link to longer explanations on the 
website.

Original comment by renggli on 18 Jan 2009 at 5:08

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

#renderOn: doesn't really work because there is more than one possible way to 
render
an exception. Also, you don't know what renderer might get passed in.

I renamed the method.

Original comment by [email protected] on 20 Feb 2009 at 5:13

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****