1. 25 Apr, 2012 6 commits
  2. 22 Apr, 2012 4 commits
  3. 20 Apr, 2012 7 commits
  4. 19 Apr, 2012 8 commits
  5. 17 Apr, 2012 1 commit
    • Pekka Paalanen's avatar
      Fix printf format warnings · b7c7963f
      Pekka Paalanen authored
      connection.c:530: warning: format '%lu' expects type 'long unsigned
      int', but argument 2 has type 'unsigned int'
      
      /connection.c:560: warning: format '%lu' expects type 'long unsigned
      int', but argument 2 has type 'unsigned int'
      Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <ppaalanen@gmail.com>
      b7c7963f
  6. 13 Apr, 2012 7 commits
  7. 12 Apr, 2012 4 commits
    • Neil Roberts's avatar
      Add a public header for the version number · 18a770c8
      Neil Roberts authored
      This adds a public header so that applications can get the Wayland
      version number at compile time. This can be used to make applications
      that support compiling against multiple versions of Wayland.
      
      There is a separate installed header called cogl-version.h which gets
      included by both wayland-client.h and wayland-server.h
      
      The canonical place for the version number is the configure.ac script
      which splits it into three separate m4 defines for the major, minor
      and micro version. These are copied into the generated
      wayland-version.h header using AC_SUBST. There is also a string form
      of the complete version number.
      
      The version number is now also automatically copied into the two .pc
      files.
      
      Because the major, minor and micro parts are required it is no longer
      possible to leave the version number as 'master' when building from
      git. Most projects seem to immediately bump the git repo to a fake
      version number (usually odd) after making a release so that there is
      always a relative number that can be used for comparison. This patch
      sets the git version to 0.99.0 under the assumption that the next
      release will be 1.0.0.
      18a770c8
    • Kristian H. Kristensen's avatar
      Update TODO · 8e5866a5
      Kristian H. Kristensen authored
      8e5866a5
    • Kristian H. Kristensen's avatar
      Introduce wl_signal · 6802eaa6
      Kristian H. Kristensen authored
      This is mostly renaming and consolidating the listener_list pattern
      into something more concise and reusable.
      6802eaa6
    • Kristian H. Kristensen's avatar
      Switch protocol to using serial numbers for ordering events and requests · 5535f155
      Kristian H. Kristensen authored
      The wayland protocol, as X, uses timestamps to match up certain
      requests with input events.  The problem is that sometimes we need to
      send out an event that doesn't have a corresponding timestamped input
      event.  For example, the pointer focus surface goes away and new
      surface needs to receive a pointer enter event.  These events are
      normally timestamped with the evdev event timestamp, but in this case,
      we don't have a evdev timestamp.  So we have to go to gettimeofday (or
      clock_gettime()) and then we don't know if it's coming from the same
      time source etc.
      
      However for all these cases we don't need a real time timestamp, we
      just need a serial number that encodes the order of events inside the
      server.  So we introduce a serial number mechanism that we can use to
      order events.  We still need real-time timestamps for actual input
      device events (motion, buttons, keys, touch), to be able to reason
      about double-click speed and movement speed so events that correspond to user input carry both a serial number and a timestamp.
      
      The serial number also give us a mechanism to key together events that
      are "logically the same" such as a unicode event and a keycode event,
      or a motion event and a relative event from a raw device.
      5535f155
  8. 11 Apr, 2012 1 commit
  9. 06 Apr, 2012 1 commit
  10. 03 Apr, 2012 1 commit
    • Kristian H. Kristensen's avatar
      shm: Allocate shm buffers through new wl_shm_pool interface · aa777e5b
      Kristian H. Kristensen authored
      There's a big cost to setting up and tearing down a mmap and faulting in
      the pages to back it.  For cases where we're continuously reallocating
      shm wl_buffers (resizing a surface, typically) it is a big performance
      improvement to be able to reuse a mmap area.  This change makes the shm
      buffer allocation a two step process: first allocate a wl_shm_pool, then
      allocate a buffer from the pool.  The wl_shm_pool encapsulate the shared
      memory pool, and lets clients allocate wl_buffers backed by chunks of that
      memory.  Buffers are allocated at an offset into the pool, so it's possible
      to create multiple buffers from one pool, for example for icons or cursor
      images.
      aa777e5b