[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ide-dev] Yet another article advising to leave Eclispe
|
Take the time to think it through. Outside of errors that affect the
stability of the entire IDE, you have to look at the context to know whether
an error dialog is necessary.
Consider a simple browse button that pops a dialog. Suppose you hit an
unexpected exception as part of populating this dialog. It's not a case
that's fatal to the entire IDE, so you don't show an error dialog. From
user's perspective, they pressed a button and nothing happened. Let's press
it again a few dozen times. That's the most benign case. It gets worse for
actions that don't have a visual manifestation of success as the user will
assume that the action has succeeded when in fact, it has failed.
- Konstantin
-----Original Message-----
From: ide-dev-bounces@xxxxxxxxxxx [mailto:ide-dev-bounces@xxxxxxxxxxx] On
Behalf Of Michael Scharf
Sent: Thursday, October 16, 2014 8:25 AM
To: Discussions about the IDE
Subject: Re: [ide-dev] Yet another article advising to leave Eclispe
> > I think there should be a policy to *not* show modal error dialogs
> > unless it is really fatal, like data is lost or the application runs
> > out of memory.
On 2014-10-16 16:41, Konstantin Komissarchik wrote:
> Applying such guidance literally would lead to usability problems of
> its own. There are times when you can minimize the prominence of an
> error (only log, no dialog) and there are times you cannot. Some
> examples that fall on both sides.
>
> Omit error dialog:
>
> 1. Background process, like a builder or an indexer
>
> 2. Operations in editors that can be reasonably degraded, like syntax
> coloring and completions
absolutely agreed! I said:
> > I think there should be a policy to *not* show modal error dialogs
> > unless it is really fatal, like data is lost or the application runs
> > out of memory.
> Don't omit error dialog:
>
> 1. A complete failure of the primary function of a wizard or an action
>
> 2. java.lang.Error (OOM, stack overflow, etc)
I don't think a stack overflow should show the error dialog. What can the
user do? Unless it constantly happens, occasional unhandled Errors should
not pop up the error dialog. Out Of Memory is different, because the IDE
gets unusable after that error.
Therefore, I agree with Eric:
+1 for not showing an error dialog unless it's the one that says "Would
+you like to exit eclipse?"y the
The error dialog only pops up, if there is an exception thrown that was not
anticipated by the responsible plugin(s). The user cannot do much, unless
maybe to remove the responsible plugin. But finding the 'bad guy' is not
easy and most users won't be able to do that....
Michael
> - Konstantin
>
> *From:*ide-dev-bounces@xxxxxxxxxxx
> [mailto:ide-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Eric Moffatt
> *Sent:* Thursday, October 16, 2014 7:07 AM
> *To:* Michael Scharf; Discussions about the IDE
> *Subject:* Re: [ide-dev] Yet another article advising to leave Eclispe
>
> +1 for not showing an error dialog unless it's the one that says
> +"Would you like to exit eclipse?",
>
> Eric
>
>
> Inactive hide details for Michael Scharf ---10/16/2014 09:14:21
> AM---On 2014-10-15 16:16, John Arthorne wrote: > I thought it wMichael
> Scharf ---10/16/2014 09:14:21 AM---On 2014-10-15 16:16, John Arthorne
> wrote: > I thought it was fairly balanced overall, listing pros a
>
> From:
>
>
>
>
> Michael Scharf <eclipse@xxxxxxxxx <mailto:eclipse@xxxxxxxxx>>
>
> To:
>
>
>
>
> Discussions about the IDE <ide-dev@xxxxxxxxxxx
> <mailto:ide-dev@xxxxxxxxxxx>>,
>
> Date:
>
>
>
>
> 10/16/2014 09:14 AM
>
> Subject:
>
>
>
>
> Re: [ide-dev] Yet another article advising to leave Eclispe
>
> Sent by:
>
>
>
>
> ide-dev-bounces@xxxxxxxxxxx <mailto:ide-dev-bounces@xxxxxxxxxxx>
>
> ----------------------------------------------------------------------
> ----------------------------------------------------------------------
> ----------------------------------------------------------------------
> ------------------------------
>
>
>
>
> On 2014-10-15 16:16, John Arthorne wrote:
>> I thought it was fairly balanced overall, listing pros and cons of each
IDE.
>> Does anyone know what the 'random
>> NullPointerException/IllegalArgumentException
>> exception alerts. " is all about?
>
> On this thread, there has been a discussion about exceptions that are
> happening in the background and logged. That is bad but it usually
> does not add to the perceived quality of the IDE. What really gets
> annoying is when a modal dialog pops up telling me that he parser for
> language X had a NullPointerException. And it gets *very* annoying
> when such a dialog pops up again and again. Those dialogs really
> damage the reputation of eclipse, independent of which plugin is
> actually responsible for the error.
>
> I think there should be a policy to *not* show modal error dialogs
> unless it is really fatal, like data is lost or the application runs
> out of memory.
>
> It's not about the actual quality -- it is about the perceived quality
> of a product. I have no idea how many exceptions happen in the
> background when I use intellij, because it does not tell me. Therefore
> I have the feeling it has a much better quality.
>
>
> Michael
>
>
>
> _______________________________________________
> ide-dev mailing list
> ide-dev@xxxxxxxxxxx <mailto:ide-dev@xxxxxxxxxxx> To change your
> delivery options, retrieve your password, or unsubscribe from this
> list, visit https://dev.eclipse.org/mailman/listinfo/ide-dev
>
>
>
>
> _______________________________________________
> ide-dev mailing list
> ide-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ide-dev
>
_______________________________________________
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit https://dev.eclipse.org/mailman/listinfo/ide-dev
