make WAWalkbackErrorHandler
Locked
 
|
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 [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: make WAWalkbackErrorHandler
|
|
Hi Esteban, "Allow debugging of errors" and in this case all applications you will register use WAWalkbackErrorHandlerI do it by going to "localhost:YourPort/", then I click on Configure in the right panel just below Browse and then I check 2015-12-23 8:40 GMT+01:00 Esteban Lorenzano <[hidden email]>: Hi, _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Hi Thomas, I’m talking about students: *they* don’t know and is a pity. I want it to be default because then they can debug their programs without needing to learn the configuration interfase (which we all know is not very… easy to use). Also my argument is: default installation is already prepared for development (hence the toolbar at the bottom), so… why not to prepare it completely for development by making WAWalkbackErrorHandler default? Esteban ps: added “default” in subject because I obviously forget that this morning :)
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: make WAWalkbackErrorHandler
|
|
In reply to this post by EstebanLM
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 <[hidden email]> 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 > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
«
Return to Seaside General
|
1 view|%1 views
| Free forum by Nabble | Edit this page |