On Mon, May 21, 2012 at 10:21 AM, Chris Muller <asqueaker at gmail.com> wrote:

> Ok, those are good things.  However, they are exceptional cases.  The
> 99% case is the pre-debugger opens and you've got to click to get a
> usable debugger.
>
> Any objections to the pre-debug notifier being an optional preference?


Also the pre-debug notifier offers "define it" for MNUs, which is *hugely*
useful.  So if you make this an optional preference *please* implement
Define It in the debugger.

On Mon, May 21, 2012 at 4:17 AM, Bert Freudenberg <bert at freudenbergs.de>
> wrote:
> >
> > On 21.05.2012, at 05:20, David T. Lewis wrote:
> >
> >> On Sun, May 20, 2012 at 06:11:18PM -0500, Chris Muller wrote:
> >>> What is the purpose of the pre-debug notifier window?
> >>
> >> Presumably it's to give you the option of not opening a debugger.
> >>
> >> There are probably lots of cases in which you might not want to
> >> open the full debugger. One example might be if you were trying to
> >> get the debugger working under ToolBuilder in MVC, in which case
> >> you might appreciate being able to at least open a simple notifier
> >> even though the rest of the debugger UI is not yet working.
> >>
> >> Another case might be when you get into one of those runaway error
> >> conditions that starts putting up notifiers all over the place
> >> while you are frantically pounding on <alt><period> to try to get
> >> it to stop. Not that this has ever happened to me of course ;)
> >>
> >> Dave
> >
> > Also, the pre-debug notifier used to be customizable. E.g. in a deployed
> application, the "debug" button was replaced by a "send log" button.
> >
> > - Bert -
> >
> >
> >
>
>


-- 
best,
Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20120521/2807f313/attachment.htm