Review Request 126515: [DrKonqi] RFC: Support showing a StatusNotifierItem instead of bringing up the dialog right away

[Ken Vermette]

> On Dec. 29, 2015, 11:56 p.m., Ken Vermette wrote:
> > In regards to the message displayed (as mentioned in your G+ post) how about:
> > 
> > "Sorry for the inconvenience. Please report the error to help improve this software."
> 
> Kai Uwe Broulik wrote:
>     I'm quite indifferent on the wording: http://wstaw.org/m/2015/12/30/canadiankonqi.jpg
>     
>     Btw, perhaps we could give the DrKonqi dialog a slightly cuter look with a sad Konqi in there, or so, similar to our about dialog. The current heart monitor icon we currently have at the right is a bit dated.
> 
> Kai Uwe Broulik wrote:
>     You know, like this: http://wstaw.org/m/2015/12/30/konqikonq.jpg except with a less cheerful dragon :)

I think you can safely drop the "sorry" part. Looking at it software apologising is tremendously insincere anyway and it's really just useless filler at that point which distracts from the available actions. I'd use the text found in the bottom-right example of your first image (just the "please report" text), and keep it at that.

We definitly need to update the graphics in the dialog itself, if for no other reason than the fact that it's clearly outdated. I'd hesitate to use Konqi even though I love the little guy, for a couple of reasons; 
- Showing a cartoon character after an application crash feels unprofessional, maybe a bit like we don't take stability seriously.
- If anyone knows the game "Duck Hunt" you'll know why we don't want the users associating failure with Konqui in the same way users loath seeing the Duck Hunt dog. "That f'ing dragon" syndrome, especially if they must work with an unstable application and see our mascot repeatedly.
- Non-KDE applications can (in some cases) spawn the dialog, so showing KDE-branded characters could make it look like it was the fault of Plasma/KDE Frameworks. Plus, it future-proofs things a bit depending on how we want to apply the dialog.

I'll rattle the VDG folks and see what we come up with, but for now we can probably agree the artwork as out-of-scope for this issue.


- Ken


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/126515/#review90316
-----------------------------------------------------------


On Dec. 29, 2015, 9:19 p.m., Kai Uwe Broulik wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/126515/
> -----------------------------------------------------------
> 
> (Updated Dec. 29, 2015, 9:19 p.m.)
> 
> 
> Review request for KDE Frameworks, Plasma, KDE Usability, and Martin Gräßlin.
> 
> 
> Repository: plasma-workspace
> 
> 
> Description
> -------
> 
> This adds a new "--passive" option to DrKonqi where it will only show a StatusNotifierItem rather than bringing up the crash dialog right away.
> 
> This can be useful for auto-restarting shell services (like plasmashell, krunner, kded) to improve the perceived quality of the product.
> 
> On Windows RT, for example, the guidelines even explicitly say "rather just dump the user on the home screen than telling him something went wrong, so he can just quickly start the app again instead of being annoyed by an error message". On iOS you also just get dropped on the home screen. Windows desktop shows a "Searching for a solution" dialog which was *the* major annoyance when something crashed, rather than the actual crash.
> 
> Video here: https://www.youtube.com/watch?v=t0ZLs-juYKc
> 
> 
> Diffs
> -----
> 
>   drkonqi/CMakeLists.txt eaeaad4 
>   drkonqi/main.cpp 7cbaae7 
>   drkonqi/statusnotifier.h PRE-CREATION 
>   drkonqi/statusnotifier.cpp PRE-CREATION 
> 
> Diff: https://git.reviewboard.kde.org/r/126515/diff/
> 
> 
> Testing
> -------
> 
> I crashed plasmashell, it restarted so fast that you didn't even have a black screen inbetween, just the panel restarting. Afterwards I got a SNI which opened DrKonqi when tapped.
> 
> The SNI disappears after 1 minute because if you didn't bother to look after it by then, you probably forgot what you did to cause the crash anyway :)
> 
> 
> Thanks,
> 
> Kai Uwe Broulik
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20160104/30396dff/attachment-0001.html>