[prev in list] [next in list] [prev in thread] [next in thread]
List: kwin
Subject: Re: focus tracking
From: Jeremy Whiting <jpwhiting () kde ! org>
Date: 2010-06-28 1:07:50
Message-ID: AANLkTildnXTDYuWMZ8qTPDCilDlXA_lz4Vr8Pgxrt5H2 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Jos,
Answers are inline.
On Sun, Jun 27, 2010 at 4:28 AM, Jos Poortvliet <jospoortvliet@gmail.com>wrote:
> On Sunday 27 June 2010 12:27:48 Jos Poortvliet wrote:
> > Dear friends,
> >
> > At LinuxTag we were approached with some questions concerning
> accessability. Among other things, it was about screen reader support and
> zooming.
>
Screen reader support in qt and kde is not quite there yet unfortunately.
There is a bridge for qt accessibility to at-spi2 which will be what gnome 3
uses, is D-Bus based, and should be workable, but it's not quite complete.
Once that is working completely however, all Qt and KDE applications should
be accessible to screen readers such as orca. On the windows and mac
platforms our stuff should be accessible to screen readers on those
platforms already.
> KMag can zoom in nicely, but does not follow the focus of the cursor (only
the mouse). This is a major issue. Does anyone know if it is possible to let
it follow the cursor?
It is wanted that it follow the text cursor? I don't think that would be
too hard but I doubt it's in there already.
regards,
Jeremy
P.S. we will have an accessibility BoF at akademy and I'm hoping any
interested parties will be there. Especially the simon developer(s) and if
the schmidt's make it to akademy it will be good to meet them and get their
feedback on the state of things also.
> The same question for the KWin full-screen zoom plugin: it only focusses
on the mouse, not the cursor, hence you can not track what you're typing.
Can we solve this somehow?
>
> Any input very welcome, this is a rather important blocker for some
deployments, esp in governments.
>
> Cheers,
> Jos
>
And an additional question:
> does anyone have any hints for a nice touchscreen device? I know the
> openSUSE booth has a set of touchscreen devices, what hardware is that?
>
> cheers and tnx,
> Jos
>
[Attachment #5 (text/html)]
Jos,<br><br>Answers are inline.<br><br><div class="gmail_quote">On Sun, Jun 27, 2010 \
at 4:28 AM, Jos Poortvliet <span dir="ltr"><<a \
href="mailto:jospoortvliet@gmail.com">jospoortvliet@gmail.com</a>></span> \
wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div \
class="h5">On Sunday 27 June 2010 12:27:48 Jos Poortvliet wrote:<br> > Dear \
friends,<br> ><br>
> At LinuxTag we were approached with some questions concerning accessability. \
Among other things, it was about screen reader support and \
zooming.<br></div></div></blockquote><div class="h5"><br>Screen reader support in qt \
and kde is not quite there yet unfortunately. There is a bridge for qt accessibility \
to at-spi2 which will be what gnome 3 uses, is D-Bus based, and should be workable, \
but it's not quite complete. Once that is working completely however, all Qt and \
KDE applications should be accessible to screen readers such as orca. On the windows \
and mac platforms our stuff should be accessible to screen readers on those platforms \
already.<br> <br>
> KMag can zoom in nicely, but does not follow the focus of the cursor (only the \
mouse). This is a major issue. Does anyone know if it is possible to let it follow \
the cursor?<br><br>It is wanted that it follow the text cursor? I don't think \
that would be too hard but I doubt it's in there already.<br>
<br><br>regards,<br>Jeremy<br><br>P.S. we will have an accessibility BoF at akademy \
and I'm hoping any interested parties will be there. Especially the simon \
developer(s) and if the schmidt's make it to akademy it will be good to meet them \
and get their feedback on the state of things also.<br> <br><br>
> The same question for the KWin full-screen zoom plugin: it only focusses on the \
mouse, not the cursor, hence you can not track what you're typing. Can we solve \
this somehow?<br> ><br>
> Any input very welcome, this is a rather important blocker for some deployments, \
esp in governments.<br> ><br>
> Cheers,<br>
> Jos<br>
><br>
<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">And an additional question:<br> \
does anyone have any hints for a nice touchscreen device? I know the openSUSE booth \
has a set of touchscreen devices, what hardware is that?<br> <br>
cheers and tnx,<br>
<font color="#888888">Jos<br>
</font></blockquote></div><br>
_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic