2010/7/22 Denis Kudriashov <[email protected]> > Yes, I can do this. > > But I hope there is existed solution. > > I was think scriptLoader>>cleanForProduction do this (disable debugger). > > I think I don't agree. That is not cleaning, but a matter of bussines. I know a lot of seaside apps running headless with RFB...in that case I do want a debugger.
But I agree, it would be good to have a Strategy and 2 implementation. DebuggerUnhandledError and TranscriptUhandledError. You put the first as default. Then, you put the straegy as an (class?) instVar of UnhandledError. you define an api method and implement it in both. Then, at runtime, in your app you can set that insVar and you are done. In addition, it can be added to Core and you create a setting that let you choose the strategy. Cheers Mariano > 2010/7/22 Stéphane Ducasse <[email protected]> > > have a look at the handler of >> >> UnhandledError>>defaultAction >> >> ^ UIManager default unhandledErrorDefaultAction: self exception >> >> so you can define a different UIManager for example >> >> Stef >> On Jul 22, 2010, at 1:18 PM, Denis Kudriashov wrote: >> >> > Hello >> > >> > Is it possible write all exceptions to log and dont show debugger? >> > How I can do this? >> > _______________________________________________ >> > Pharo-project mailing list >> > [email protected] >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
