<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 26.10.2016 08:57, Alexis BRENON @Wayland wrote:<br>
<br>
@Raster: Thank you for your reminder.<br>
<br>
Maybe Enlightenment with Tiling2 and kinetic scrolling is already
what you need.<br>
<br>
If I remember correctly I3 (<a class="moz-txt-link-abbreviated" href="http://www.i3wm.org">www.i3wm.org</a>)<a rel="nofollow"
class="external text" href="http://i3wm.org/"></a> might work
together with Wayland as well.<br>
<br>
In general, I have seen at all major toolkits transistion efforts to
Wayland since around 2 years. Some have matured while others are
experimental so to say.<br>
<br>
<br>
<br>
Best Regards<br>
Christian Stroetmann<br>
<br>
<blockquote
cite="mid:CAJPB9o0DCTtnCTpe8pPjyO=R6p3Y-M2XzXxM3W7yWhJKokxDQw@mail.gmail.com"
type="cite">
<div dir="ltr">Just to be sure that I understand clearly, what you
call 'Toolkit' is libraries like GTK, Qt, and co. that are used
by developers to build their apps, isn't it ?
<div><br>
</div>
<div>Finally, do you know some tiling DE/WM Wayland compliant ?</div>
<div><br>
</div>
<div>Kind,<br>
Alexis.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">Le mer. 26 oct. 2016 à 02:17, Carsten Haitzler
<<a moz-do-not-send="true"
href="mailto:raster@rasterman.com">raster@rasterman.com</a>>
a écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, 24
Oct 2016 18:42:31 +0000 "Alexis BRENON @Wayland"
<brenon.alexis<br class="gmail_msg">
+<a moz-do-not-send="true" href="mailto:wayland@gmail.com"
class="gmail_msg" target="_blank">wayland@gmail.com</a>>
said:<br class="gmail_msg">
<br class="gmail_msg">
> Hello everyone,<br class="gmail_msg">
><br class="gmail_msg">
> I would like to implement kinetic scroll in the libinput
driver for Xorg.<br class="gmail_msg">
><br class="gmail_msg">
> I know that it's probably not the intended use of
libinput ; as explained<br class="gmail_msg">
> in the documentation, it's the client that have to manage
that.<br class="gmail_msg">
><br class="gmail_msg">
> However, as an Xorg user not happy with the synaptics
driver, I would like<br class="gmail_msg">
> to add a similar feature (fixing small disagreements
encountered with<br class="gmail_msg">
> synaptics) to libinput, allowing Xorg users to easily
move to libinput<br class="gmail_msg">
> without losing this feature.<br class="gmail_msg">
><br class="gmail_msg">
> My first idea is to implement the kinetic scroll using a
thread that sends<br class="gmail_msg">
> axis events as long as there is no button event, key
event or motion event<br class="gmail_msg">
> higher than a threshold.<br class="gmail_msg">
><br class="gmail_msg">
> It makes some time since the last time I developed in C,
and maybe it's not<br class="gmail_msg">
> the better way to do it. I would be happy to hear your
advices.<br class="gmail_msg">
><br class="gmail_msg">
> One thing I'm thinking of is then to add some options in
the Xorg<br class="gmail_msg">
> configuration file to enable/disable this feature, choose
the events<br class="gmail_msg">
> stopping the kinetic scroll and change some thresholds.
This will allow to<br class="gmail_msg">
> easily disable this feature in the future in case the
clients manage the<br class="gmail_msg">
> kinetic scroll on their own.<br class="gmail_msg">
><br class="gmail_msg">
> What do you think of this? Is there someone already
working on it? Is my<br class="gmail_msg">
> proposition a good way to implement it?<br
class="gmail_msg">
><br class="gmail_msg">
> Thanks for your attention.<br class="gmail_msg">
><br class="gmail_msg">
> Kind regards,<br class="gmail_msg">
> Alexis BRENON.<br class="gmail_msg">
<br class="gmail_msg">
we already do kinetic scrolling higher up in the toolkit. we
do acceleration<br class="gmail_msg">
using these events and we do smooth animated scrolling in our
scroller and not<br class="gmail_msg">
just stepping, as well as momentum as we slid with bouncing at
the ends. it's<br class="gmail_msg">
already done in toolkit out of the box. if you try and hack
this in at the<br class="gmail_msg">
input layer this simply doubles the amount of this and likely
makes the user<br class="gmail_msg">
experience worse. this would have to be off by default and if
it's off by<br class="gmail_msg">
default... you need ways of turning it on client by client ...
and even then<br class="gmail_msg">
there are a pile of other problems you'll hit. so my
suggestion is - don't. add<br class="gmail_msg">
to your favorite toolkits instead if they don't have it. they
have far more<br class="gmail_msg">
information about the context at the time and the use cases
needed etc.<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
--<br class="gmail_msg">
------------- Codito, ergo sum - "I code, therefore I am"
--------------<br class="gmail_msg">
The Rasterman (Carsten Haitzler) <a moz-do-not-send="true"
href="mailto:raster@rasterman.com" class="gmail_msg"
target="_blank">raster@rasterman.com</a><br
class="gmail_msg">
<br class="gmail_msg">
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wayland-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wayland-devel@lists.freedesktop.org">wayland-devel@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="https://lists.freedesktop.org/mailman/listinfo/wayland-devel">https://lists.freedesktop.org/mailman/listinfo/wayland-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>