So what to do? Should I back out the change?
At 10:33 26/08/2010, Nick Ager wrote:Seaside provides general mechanisms. More specific solutions depend on the end-user community that one targets. In my experience, I had happy end-users with a simple dialog box asking their agreement to communicate their execution stack, knowing that that context may contain proprietary information.
is there a problem changing WAWalkbackErrorHandler to something that makes more sense to the end user?
Regards,
Reza
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki