Go go go! Stef
> On 10 Jul 2019, at 20:21, Cyril Ferlicot D. <cyril.ferli...@gmail.com> wrote: > > Hi, > > After talking with Steven (in copy) we agreed on possible improvements > around the pre debugger. I would like to share our vision and check if > the community agrees. > > Context: > > The pre debugger is the window opening when an exception is signalled > and not catched. This window currently has two views: > - On warnings it display a text explaining the encountered problem. You > can the proceed, abandon or debug. For example, this happens on > Deprecations. > - On other exceptions it display a short stack of the context in which > the error was raised. You can abandon, open a full debugger, ... > > Before, both views were managed via the same UI class. Yesterday I > slitted this class. > > Proposed change: > > In our opinion, the pre debugger displaying a stack is useless. All the > options it proposes are in the full debugger within one click reach. The > only value we see for the pre debugger is about warnings. > > Thus, we propose to remove the stack pre debugger and display directly > the full debugger for anything else than a warning. This will save > everyone one click each time we want to debug something. We would keep > the textual view for warnings. > > In case we do this, I wonder if we should keep the setting "Open full > debugger". I think most users of this option are using it in order to > not see the stack pre debugger and not to skip warnings. So, do someone > have an opinion about keeping or removing this setting in case we remove > the stack pre debugger? > > Possible future changes: > > In the future I would also like it if the opening of the pre (or full) > debugger would be delegated to the raised exception in order to allow > the introduction of different pre debuggers. But it's just an idea and > not the scope of this mail. :) > > -- > Cyril Ferlicot > https://ferlicot.fr >
