Re: make WAWalkbackErrorHandler
Johan Brichau <[email protected]>
| Newsgroups | gmane.comp.lang.smalltalk.squeak.seaside |
|---|---|
| Message-ID | <[email protected]> |
Yes, that’s indeed a sensible default. I changed it for 3.2.0 now. Mind that the Seaside Welcome >> Basic Configuration has an option to check: "Allow debugging of errors” So, no need to dive into the more advanced configuration for that. cheers Johan > On 23 Dec 2015, at 08:40, Esteban Lorenzano <[email protected]> wrote: > > Hi, > > So, I’m in Togo teaching Pharo and Seaside to students, and part of the course is to make a small application (they have 3 days for doing it). The first blocking issue they have is that since default error handler is WAHtmlErrorHandler they are lost each time they made a simple mistake (WAHtmlErrorHandler eats rendering problems, for example… or just shows DNU without saying anything. > And of course showing the students the configuration interfase is overkill :) > > Now, since the default registration includes the toolbar, meaning than by default we have a “development app” (A correct approach, IMO), I wonder if we couldn’t put WAWalkbackErrorHandler as default as well? (I remember previous versions of Seaside had it, but it had changed since then). > > cheers, > Esteban > > _______________________________________________ > seaside mailing list > [email protected] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside