[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    error reporting in kcm_keyboard and kded_keyboard
From:       Andriy Rysin <arysin () gmail ! com>
Date:       2010-08-21 0:39:38
Message-ID: AANLkTim-7Y+S33eB=Or2gwREcUmFYU6eUwSDxsL0Nz9a () mail ! gmail ! com
[Download RAW message or body]

Keyboard module has to handle gracefully (without crashing) the situation
when something is missing for its work (e.g. evdev.xml rules file can't be
found).
We need this in both kcm UI and when keyboard kded daemon starts. BTW in kcm
UI such errors disable only part of the functionality (mainly 2nd and 3rd
tabs) while hardware tab can still work so I was thinking of something like
this screenshot (
http://dict.linux.org.ua/other/showing_error_in_kcm_keyboard.png). But may
be there's better/common way to do it.

For kded I guess it could be KNotification but I haven't looked at it close
yet.

The question is what's the best/common way to do both error notifications.

Thanks,
Andriy

[Attachment #3 (text/html)]

Keyboard module has to handle gracefully (without crashing) the 
situation when something is missing for its work (e.g. evdev.xml rules 
file can&#39;t be found).<br>We need this in both kcm UI and when keyboard 
kded daemon starts. BTW in kcm UI such errors disable only part of the 
functionality (mainly 2nd and 3rd tabs) while hardware tab can still 
work so I was thinking of something like this screenshot (<a \
href="http://dict.linux.org.ua/other/showing_error_in_kcm_keyboard.png">http://dict.linux.org.ua/other/showing_error_in_kcm_keyboard.png</a>). \
But may be  there&#39;s better/common way to do it.<br>
<br>For kded I guess it could be KNotification but I haven&#39;t looked at it close \
yet.<br><br>The question is what&#39;s the best/common way to do both error \
notifications.<br><br>Thanks,<br><font color="#888888">Andriy</font>



[prev in list] [next in list] [prev in thread] [next in thread]