<p dir="ltr"><br>
On Aug 19, 2014 5:04 AM, "Pekka Paalanen" <<a href="mailto:ppaalanen@gmail.com">ppaalanen@gmail.com</a>> wrote:<br>
><br>
> On Wed, 6 Aug 2014 19:07:50 -0400<br>
> Stephen Chandler Paul <<a href="mailto:thatslyude@gmail.com">thatslyude@gmail.com</a>> wrote:<br>
><br>
> > Hi! As some of you have been aware, I have been working on implementing tablet<br>
> > ssupport in libinput, the wayland protocol and weston. This patchset adds basic<br>
> > tablet support to weston, along with support in the shell and the window<br>
> > manager. It should be noted that these patches rely on one of the earlier<br>
> > patches to libinput that I posted on the mailing list: "tablet: Add<br>
> > libinput_tablet_has_axis()", along with the tablet-support branch in the git repository for libinput.<br>
> ><br>
> > As of right now, the following things are still missing/haven't been finished<br>
> > yet:<br>
> > * Tablet objects don't ever send a removed event, right now it's up to the<br>
> > clients to free the resources for each tool object.<br>
> > * Tablet tool objects should be separate for each tablet connected that doesn't<br>
> > report serial numbers. Right now tablet objects are shared by all tablets<br>
> > connected to the system unconditionally.<br>
> > * The tablet cursor disappears occasionally when moving a window and causing<br>
> > the mouse pointer to change images, but reappears the next time a client sets<br>
> > a cursor image.<br>
> > * weston-flower can crash the shell for some reason. It seems that if a tablet<br>
> > is turned on, and the first surface the tool comes into focus on belongs to a<br>
> > weston-flower instance, the desktop-shell runs into an error and exits. I<br>
> > haven't noticed this with anything other then weston-flower though.<br>
> > * Held down buttons are released when the tool changes focus from one surface<br>
> > to another, instead of being held down until they're released.<br>
> > * Some of the declarations for structs in my code might need to be moved<br>
> > around, I'm not sure what the expected guidelines for this in weston's code<br>
> > are though.<br>
> > * A surface argument needs to be added to the proximity_out event, so we can<br>
> > tell if the tablet tool is leaving proximity to switch focus to another<br>
> > surface, or if it's just exiting proximity.<br>
> ><br>
> > Review/critique would be appreciated, thank you! ^^<br>
> ><br>
> > Cheers,<br>
> > Lyude<br>
> ><br>
> > Stephen Chandler Paul (19):<br>
> > tablet: Add XML for wl_tablet and wl_tablet_manager<br>
> > tablet: Add initial tablet support to weston<br>
> > client: Add support for handling motion events in toytoolkit<br>
> > client: Add support for handling proximity_in/out events in<br>
> > libtoytoolkit<br>
> > tablet: Add support for setting/changing the tablet cursor in weston<br>
> > client: Add tablet cursor support into libtoytoolkit<br>
> > tablet: Add support for tablet tool objects<br>
> > client: Add support for tool objects in libtoytoolkit<br>
> > client: Add support for tablet cursor motion to window frames in<br>
> > libtoytoolkit<br>
> > tablet: Add support for button presses to weston<br>
> > client: Add support for handling button presses to libtoytoolkit<br>
> > tablet: Add support for up/down events to weston<br>
> > client: Add up/down event support into libtoytoolkit<br>
> > tablet: Add support for moving windows around using the stylus<br>
> > tablet: Add support for reporting pressure, distance, and tilt in<br>
> > weston<br>
> > client: Add support for pressure, distance, and tilt into<br>
> > libtoytoolkit<br>
> > tablet: Add tablet support to the top panel of the desktop shell<br>
> > tablet: Add binding to activate surfaces using the tablet tool<br>
> > tablet: Add demo application for tablets<br>
> ><br>
> > .gitignore | 1 +<br>
> > Makefile.am | 23 +-<br>
> > clients/desktop-shell.c | 55 ++++<br>
> > clients/tablet.c | 341 ++++++++++++++++++++<br>
> > clients/window.c | 607 ++++++++++++++++++++++++++++++++++++<br>
> > clients/window.h | 102 ++++++<br>
> > desktop-shell/shell.c | 282 +++++++++++++++++<br>
> > protocol/wayland-tablet.xml | 310 +++++++++++++++++++<br>
> > shared/cairo-util.h | 4 +<br>
> > shared/frame.c | 38 +++<br>
> > src/bindings.c | 37 +++<br>
> > src/compositor.c | 1 +<br>
> > src/compositor.h | 171 ++++++++++<br>
> > src/input.c | 736 ++++++++++++++++++++++++++++++++++++++++++++<br>
> > src/libinput-device.c | 317 +++++++++++++++++++<br>
> > src/libinput-device.h | 4 +-<br>
> > 16 files changed, 3024 insertions(+), 5 deletions(-)<br>
> > create mode 100644 clients/tablet.c<br>
> > create mode 100644 protocol/wayland-tablet.xml<br>
> ><br>
><br>
> Hi,<br>
><br>
> just a heads-up, do I get the right impression that this is not yet in<br>
> a shape to merge into Weston, so won't be included in 1.6?<br>
><br>
> Could an input person review this and suggest whether this should in<br>
> his opinion get merged for 1.6 and is it reasonable to assume, that all<br>
> the remaining known bugs can be sufficiently fixed within the couple<br>
> of weeks or so that our alpha and RC phase lasts?<br>
><br>
> I still haven't read the latest protocol discussion thread, so I'm not<br>
> sure where the design is atm.<br>
><br>
> Personally I cannot even test this, since I don't have a tablet device<br>
> here.<br>
><br>
><br>
> Thanks,<br>
> pq</p>
<p dir="ltr">I've the opposite problem: lots of hardware to test with (the basic results of which I've given to Lyude directly) but still nowhere near enough familiarity with Wayland/Weston to provide competent feedback on the patches themselves. If anyone has questions about design decisions I can try to add light to the discussion with use-case information, but I'm not yet able to see potential problems on my own...</p>
<p dir="ltr">Jason G.<br>
</p>