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

(Updated Dez. 27, 2015, 4:11 nachm.)


Review request for KDE Frameworks, Plasma, KDE Usability, and Martin Gräßlin.


Changes
-------

Variant 2: Use a desktop notification for "regular" crashes.

When the passive argument is not set (the default), a desktop notification will 
be spawned instead of the full-blown DrKonqi dialog [1]. In the notification a 
user can either choose to restart the app (after which the SNI stays in systray 
for the remaining minute in case he wants to report a bug nonetheless) or 
report a bug straight away (same as clicking the SNI, the SNI goes away and 
DrKonqi appears).

In case no notification service is running (eg. plasma crashed or non 
xdg-compliant desktop environment) regular DrKonqi appears directly. This also 
happens when Plasma crashes three times in a row where it'll refrain from 
restarting (see Review 126517) - you won't have a systray anymore then, so full 
DrKonqi pops up as well.

(There's an unused include and member variable in statusnotifier.h, I removed 
it locally)

[1] http://wstaw.org/m/2015/12/25/drkonqipassive.png


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 (updated)
-----

  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

_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Reply via email to