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

List:       kde-panel-devel
Subject:    Re: MediaBrowser Zoom levels
From:       Christophe Olinger <olingerc () binarylooks ! com>
Date:       2010-04-15 17:32:04
Message-ID: u2q1718db771004151032g762566d9vfd0c5c53706ecb21 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Thu, Apr 15, 2010 at 6:26 PM, Aaron J. Seigo <aseigo@kde.org> wrote:

> On April 15, 2010, Marco Martin wrote:
> > I'm leaning towards banning double click at all there :)
>
> absolutely. and here's why: there is no double click with a remote control.
>
> PMC must not be designed for a mouse. it must be designed for a single
> pointer
> with low accuracy with key-based activation as a secondary option.
>
> this covers:
>
> * traditional t.v. remote
> * wiimote
> * fingers on a touch screen
>
> PMC can not assume for a moment that a mouse is anywhere near it. if it
> works
> on the above, then with a mouse one will also be just fine.
>
>
Right. Let's start from the most common denominator and see how/if we
can/want to adapt later to more specific controls.

Byebye hover :-)


> --
> Aaron J. Seigo
> humru othro a kohnu se
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
>
> KDE core developer sponsored by Qt Development Frameworks
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel@kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>

[Attachment #5 (text/html)]

<br><br><div class="gmail_quote">On Thu, Apr 15, 2010 at 6:26 PM, Aaron J. Seigo \
<span dir="ltr">&lt;<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"> <div class="im">On April 15, 2010, Marco Martin \
wrote:<br> &gt; I&#39;m leaning towards banning double click at all there :)<br>
<br>
</div>absolutely. and here&#39;s why: there is no double click with a remote \
control.<br> <br>
PMC must not be designed for a mouse. it must be designed for a single pointer<br>
with low accuracy with key-based activation as a secondary option.<br>
<br>
this covers:<br>
<br>
* traditional t.v. remote<br>
* wiimote<br>
* fingers on a touch screen<br>
<br>
PMC can not assume for a moment that a mouse is anywhere near it. if it works<br>
on the above, then with a mouse one will also be just fine.<br>
<font color="#888888"><br></font></blockquote><div><br></div><div>Right. Let&#39;s \
start from the most common denominator and see how/if we can/want to adapt later to \
more specific controls.</div><div><br></div><div>Byebye hover :-)</div> <div> \
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
                solid;padding-left:1ex;"><font color="#888888">
--<br>
Aaron J. Seigo<br>
humru othro a kohnu se<br>
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43<br>
<br>
KDE core developer sponsored by Qt Development Frameworks<br>
</font><div><div></div><div \
class="h5">_______________________________________________<br> Plasma-devel mailing \
list<br> <a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br> \
</div></div></blockquote></div><br>



_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


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