Re: [platform-ui-dev] Errors in the UI after deinstalling components

[Markus Keller <markus_keller@xxxxxxxxxx>]

"knowingly" is the key word.
We don't know whether the user knew that he started up with an install
that didn't contain the contributing plug-in, and we don't know whether
that's just a temporary condition or permanent.

As a user, I don't want to lose the
view placement/state, so the error view is exactly what I'd expect (though
I agree it could look nicer in the case the contributing plug-in is gone).

If a product has a problem with showing
an error message for a missing view, then it can implement uninstall handlers
that close a view when the contributing plug-in is uninstalled. For the
SDK, that's not necessary/desired.

> Have you seen that in any other
product?

Yes, it e.g. happens in my browser when
it tries to restore a tab, but the URL is no longer available. Or on Windows/Mac
when I open a shortcut/alias whose target is not available (may also be
a temporary condition). Most other products I use are not extensible in
a way that is comparable to Eclipse.

Markus



From:      
 Doug Schaefer <dschaefer@xxxxxxx>
To:      
 Lars Vogel <platform-ui-dev@xxxxxxxxxxx>,
"Eclipse Platform UI component        developers
list." <platform-ui-dev@xxxxxxxxxxx>
Date:      
 2014-10-12 04:24
Subject:    
   Re: [platform-ui-dev]
Errors in the UI after deinstalling components
Sent by:    
   platform-ui-dev-bounces@xxxxxxxxxxx

---

Yeah, showing a horrible
error message when the user knowingly uninstalls a feature is an acceptable
user experience is correct how? Have you seen that in any other product?
And was OK with it?

Sent from my BlackBerry 10
smartphone.

From: Lars Vogel
Sent: Friday, October 10, 2014 11:01 AM
To: Eclipse Platform UI component developers list.
Reply To: Eclipse Platform UI component developers list.
Subject: [platform-ui-dev] Errors in the UI after deinstalling components

Hi, 

if the user deinstalls a plug-in which used to be in the
current perspective we display an error, as in the following example.

<image>

IMHO this is undesired, as this gives a bad user experience.


If nobody objects and thinks that is great feature of
our IDE, we can try to fix this also in Bug 445663. IMHO we should at least
remove parts for the current UI for which the bundlessclass cannot be found
anymore in the current runtime.

Best regards, Lars  

_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev