Porting Apps to Wayland

[Joakim Sindholt]

I basically have no valid clue about how this will look when it's done,
but if you open protocol/wayland.xml you'll see the input system as it's
exposed to you the developer in its current form:

  <interface name="input_device" version="1">
    <request name="attach">
      <arg name="time" type="uint"/>
      <arg name="buffer" type="object" interface="buffer"/>
      <arg name="hotspot_x" type="int"/>
      <arg name="hotspot_y" type="int"/>
    </request>

    <event name="motion">
      <arg name="time" type="uint"/>
      <arg name="x" type="int"/>
      <arg name="y" type="int"/>
      <arg name="surface_x" type="int"/>
      <arg name="surface_y" type="int"/>
    </event>

    <event name="button">
      <arg name="time" type="uint"/>
      <arg name="button" type="uint"/>
      <arg name="state" type="uint"/>
    </event>

    <event name="key">
      <arg name="time" type="uint"/>
      <arg name="key" type="uint"/>
      <arg name="state" type="uint"/>
    </event>

    <event name="pointer_focus">
      <arg name="time" type="uint"/>
      <arg name="surface" type="object" interface="surface"/>
      <arg name="x" type="int"/>
      <arg name="y" type="int"/>
      <arg name="surface_x" type="int"/>
      <arg name="surface_y" type="int"/>
    </event>

    <event name="keyboard_focus">
      <arg name="time" type="uint"/>
      <arg name="surface" type="object" interface="surface"/>
      <arg name="keys" type="array"/>
    </event>
  </interface>

It's definitely a new interface. IIRC you might want to use the new
libxkbcommon to translate keycodes to keysyms. You will not be able to
use libxcb, and the interface will probably be easier to deal with.

On Sun, 2010-11-21 at 21:30 +0100, Kai Mast wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hey Guys,
> 
> I am pretty new to Wayland and just have a general question.
> 
> What exactly does change for me as a game developer on the programming
> site when I switch to Wayland. Obviously the OpenGL calls will be
> untouched. But what about Input? Will i still be able to use libxcb or
> will there a completely different API to handle that kind of stuff?
> 
> greets,
> Kai
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iQIcBAEBAgAGBQJM6YFsAAoJEKU5B2k1XeMEKIUP/3mCdkPWljNYrmmGAtC78CVk
> 8XHow3MjcBt6OrgU1pfbCJREUHKF848gmS4bB1IluqCAU4h15pHj8N7ujs9MiN7i
> xCNCVPLp1P+fR2pDnr1hQjJ5OAMq4/KGEN4qlug2nsXHHYY4KBZqUFsXJL4O/IaH
> YmSsNJe6urJu6dBkE1Ry1mzk7ET8UJf4s+Mtk0dl/YJUnlzUm1ZCmnkGZe3Dd8YB
> 6fPuRGTItQRJifiMOKcAw8dm9SV3m7fDDtPFRdZRz/CQ272SICSIsLWhB1n71p/0
> 3dHoIazafVApEWQjFYfbTsjGfuzGK1L/AfdpZNQc7MbsVSkQVS39gveCVS+bYBhi
> OTruRjmg7CXb0LkdhA6ZNzmDGg8SD0OJ1rj/vnzA46SBOmyIiBsr56rHJFMQfzaP
> ZxzT8y4BReD8GBe2xIuKwXtidiNSIaCLOm5zTw455JAEalv+E6BJKa6L54DJRvrx
> lqkjSevLoDzNar9WZ//kfh6oG5DtHCfZ+yxdxZZav9GuW5wo1BgPhVKshUA9o4Gy
> 8d5o3XmzmGdtXVCQyoT/7198v3UdEafjbBpjynsfVgRh2dpZXCto39Ue++eB34YX
> VTtytFPjCBCajgrr1YeLfFcVMXf6kZscB6x23CEdIryZpeXDYxVc3DIbEpwMdnnm
> lbgls9l+G9UEm+6smw+Y
> =TLrQ
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel