On Thu, Jul 11, 2019 at 4:22 PM Peter Uhnak <i.uhnak@gmail.com> wrote:
Hi Cyril,
I had a particular use-case in Sentry Logger (adopted from old ShoreLine reporter) that added a "Report" button to the pre-debugger (via a PreDebugAction subclass). Not having the button is fine for me (automated reporting is always better), just wanted to mention it.
What I am wondering more is whether eliminating the pre-debugger would make it much harder to add something like "Production pre-debug window" that contains alternative content that doesn't scare non-technical people.
Not all users of Pharo are Pharo developers, so dropping on them the full debugger is not good. Would it be cleaner to enable by default the Always Open Full Debugger, and then it can be toggled off when building production images?
Or did you have some other alternatives in mind?
Hi Peter, With changes introduced with the GTDebbuger it is possible to register alternative debuggers. They have a priority and know if they need to open depending on the context. We discussed with Steven and Thomas from the RMoD team and we think this is cool like that we can register alternative debuggers. On top of that, we would like to add the concept of fallback in case there is a problem. Currently, when the debugger bug, the emergency evaluator is open. We would like to open the next available debugger instead of the emergency evaluator. Then the emergency evaluator would be the last in the list. Also, an another subject, the button report can still be added to the full debugger.
Peter
-- Cyril Ferlicot https://ferlicot.fr