--===============7983214193943771456==
Content-Type: multipart/alternative; boundary="001a1145b81880c7fa056654f8cc"

--001a1145b81880c7fa056654f8cc
Content-Type: text/plain; charset="UTF-8"

On Mon, Feb 26, 2018 at 5:49 AM, Samuel Thibault <
samuel.thibault@ens-lyon.org> wrote:

> Hello,
>
> So, I also saw the removal of generic modules.
>
> Unfortunately we currently need it for implementing perfect zoom feature
> :)
>
> The context is that visual-impaired users need magnification of the
> desktop. Changing font sizes / dpi etc. have their limit, at some point
> we need to just have a zoomed view of a piece of the screen. Currently
> compiz' ezoom takes the piece of the screen, and magnify it to show it
> on the screen, with obviously awful pixelization effects.
>
> Our idea was very similar to gtk-vector-screenshot : instead of taking
> the output as it is displayed on the screen, get a module loaded within
> the application, with which ezoom can discuss to make the application
> produce a magnified rendering of its window, which ezoom can then show
> in the magnification glass, thus getting perfect zoom.
>
> Without module loading, I don't know how to implement it :) Or perhaps
> this could be added as an AT-SPI interface?
>
>
If it is a toolkit-level feature that is needed desktop-wide, it needs to
be implemented in the toolkit proper, not added through the backdoor via a
module. I know that this will require some rearchitecting and may not be
super-easy, but I still believe that this is the right way forward.

--001a1145b81880c7fa056654f8cc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Feb 26, 2018 at 5:49 AM, Samuel Thibault <span dir=
=3D"ltr">&lt;<a href=3D"mailto:samuel.thibault@ens-lyon.org" target=3D"_bla=
nk">samuel.thibault@ens-lyon.org</a>&gt;</span> wrote:<br><div class=3D"gma=
il_extra"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<=
br>
<br>
So, I also saw the removal of generic modules.<br>
<br>
Unfortunately we currently need it for implementing perfect zoom feature<br=
>
:)<br>
<br>
The context is that visual-impaired users need magnification of the<br>
desktop. Changing font sizes / dpi etc. have their limit, at some point<br>
we need to just have a zoomed view of a piece of the screen. Currently<br>
compiz&#39; ezoom takes the piece of the screen, and magnify it to show it<=
br>
on the screen, with obviously awful pixelization effects.<br>
<br>
Our idea was very similar to gtk-vector-screenshot : instead of taking<br>
the output as it is displayed on the screen, get a module loaded within<br>
the application, with which ezoom can discuss to make the application<br>
produce a magnified rendering of its window, which ezoom can then show<br>
in the magnification glass, thus getting perfect zoom.<br>
<br>
Without module loading, I don&#39;t know how to implement it :) Or perhaps<=
br>
this could be added as an AT-SPI interface?<br><br></blockquote><div><br></=
div><div>If it is a toolkit-level feature that is needed desktop-wide, it n=
eeds to be implemented in the toolkit proper, not added through the backdoo=
r via a module. I know that this will require some rearchitecting and may n=
ot be super-easy, but I still believe that this is the right way forward.<b=
r></div></div></div></div>

--001a1145b81880c7fa056654f8cc--

--===============7983214193943771456==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-devel-list

--===============7983214193943771456==--