'Re: [Kde-accessibility] System Bell'

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

List:       kde-accessibility
Subject:    Re: [Kde-accessibility] System Bell
From:       Peter Grasch <peter () grasch ! net>
Date:       2015-01-11 23:10:50
Message-ID: E4F2BD41-0987-40B8-B920-2B6E8E29F370 () grasch ! net
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Hello,

> On 06 Jan 2015, at 14:00, Heiko Tietze <heiko.tietze@user-prompt.com> wrote:
> The survey about system settings did reveal some confusion about the system bell \
> (i.e. there was no clear association with other settings). Most users do not even \
> know what the system bell can be used for (and even experts doubt to have the \
> hardware). But there are still people who want it for low latency audio feedback \
> [1] and notification on the console [2].
I'm sure there are some users. But correct me if I'm wrong - none of the ones you \
pointed to have a real need for the KCM as it is now. (we already have low latency \
visual feedback regardless of a visual bell)

> Nevertheless I agree with removing this feature or rather harmonizing with default \
> notification. As a notification feature you could bind the system bell to some \
> special activities, like console tasks. And disabled people adjust notifications \
> instead of accessibility, or both.
A "beep" backend for KNotify would be nice and probably reasonably easy to implement.
I think this should become a wish list item. Nevertheless, this imho shouldn't block \
the removal of the KCM.

Best regards,
Peter

[Attachment #5 (unknown)]

<html><head><meta http-equiv="Content-Type" content="text/html \
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
-webkit-line-break: after-white-space;" class="">Hello,<div class=""><br \
class=""><div><blockquote type="cite" class=""><div class="">On 06 Jan 2015, at \
14:00, Heiko Tietze &lt;<a href="mailto:heiko.tietze@user-prompt.com" \
class="">heiko.tietze@user-prompt.com</a>&gt; wrote:</div><div class=""><span \
style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: \
normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: \
auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; \
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; \
display: inline !important;" class="">The survey about system settings did reveal \
some confusion about the system bell (i.e. there was no clear association with other \
settings). Most users do not even know what the system bell can be used for (and even \
experts doubt to have the hardware). But there are still people who want it for low \
latency audio feedback [1] and notification on the console [2].</span><br \
style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: \
normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: \
auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; \
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" \
class=""></div></blockquote>I'm sure there are some users. But correct me if I'm \
wrong - none of the ones you pointed to have a real need for the KCM as it is now. \
(we already have low latency visual feedback regardless of a visual \
bell)</div><div><br class=""></div><div><blockquote type="cite" class=""><div \
class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; \
font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: \
normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; \
white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; \
float: none; display: inline !important;" class="">Nevertheless I agree with removing \
this feature or rather harmonizing with default notification. As a notification \
feature you could bind the system bell to some special activities, like console \
tasks. And disabled people adjust notifications instead of accessibility, or \
both.</span></div></blockquote>A "beep" backend for KNotify would be nice and \
probably reasonably easy to implement.</div></div><div>I think this should become a \
wish list item. Nevertheless, this imho shouldn't block the removal of the \
KCM.</div><div><br class=""></div><div>Best \
regards,</div><div>Peter</div></body></html>

_______________________________________________
kde-accessibility mailing list
kde-accessibility@kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility

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