1. 29 Nov, 2011 1 commit
  2. 23 Nov, 2011 2 commits
    • Kristian Høgsberg's avatar
      New drag and drop / selection protocol · eae3bcb4
      Kristian Høgsberg authored
      This commit brings a big change to the DND and copy/paste interfaces.
      Most importantly the functionality is now independent of wl_shell.
      The wl_shell interface is intended for desktop style UI interaction and
      an optional and experimental interface.
      The new interface also allows receiving the DND data multiple times or
      multiple times during the drag, and the mechanism for offering and receiving
      data is now shared between DND and selections.
    • Kristian Høgsberg's avatar
      server: Stop special casing the compositor · 0b7d1e86
      Kristian Høgsberg authored
      wl_compositor_init() was just adding the global and providing a helper
      bind function.  Not useful enough to warrent API.
  3. 17 Nov, 2011 1 commit
    • Kristian Høgsberg's avatar
      Introduce wl_resource_queue_event() for sending events later · 4abc56bd
      Kristian Høgsberg authored
      Some events, such as the display.delete_id, aren't very urgent and we
      would like to not always send them immdiately and cause an unnecessary
      context switch.  The wl_resource_queue_event() function will place the
      event in the connection output buffer but not request the main loop to
      poll for writable.  The effect is that the event will just sit in the
      output buffer until a more important event comes around and requires
  4. 06 Sep, 2011 1 commit
  5. 01 Sep, 2011 1 commit
  6. 31 Aug, 2011 1 commit
    • Kristian Høgsberg's avatar
      Remove the wl_visual interface · c640571c
      Kristian Høgsberg authored
      The visual interface was meant to be a generic mechanism for
      specifying the content of a buffer.  It goes back to before we had the
      buffer factory interfaces (like wl_drm and wl_shm) and we wanted to
      keep it open-ended enough that yuv, png or even svg buffer or so would
      be possible.
      Now that we have the buffer abstraction, we can add different buffer
      types by introducing new interfaces that create buffers.  It only
      makes sense to leave it to those interfaces to specify the contents of
      the buffers.
      For wl_shm, this means that we now just specify the pixel format using
      an enum.  For EGL buffers, the exact pixel formats are controlled by
      the implementation (part of wl_drm and similar), and from the client
      point of view, everything is controlled using EGLConfigs.
  7. 29 Aug, 2011 1 commit
  8. 27 Aug, 2011 5 commits
  9. 12 Aug, 2011 1 commit
  10. 29 Jun, 2011 1 commit
  11. 21 Jun, 2011 2 commits
  12. 20 Jun, 2011 1 commit
    • Laszlo Agocs's avatar
      Add wl_display_remove_global. · aae9f214
      Laszlo Agocs authored
      Change 4453ba08 disallows using
      post_global with objects not on the global list. Therefore selection
      and drag offers have to be added to the global list from now on.
      However these may often get replaced by a newer object and thus need a
      way to remove a global from the global list.
  13. 11 May, 2011 1 commit
    • Kristian Høgsberg's avatar
      Unify error events · 1db05255
      Kristian Høgsberg authored
      Consolidate the different error events into one.  This event will also be
      usable for other interaces.
  14. 06 May, 2011 1 commit
  15. 22 Apr, 2011 5 commits
  16. 21 Apr, 2011 1 commit
    • Kristian Høgsberg's avatar
      event-loop: Add an optional post-dispatch source callout · 589e581f
      Kristian Høgsberg authored
      This lets a source mark itself as ready to dispatch even though the fd
      didn't trigger.   What can happen is that for the X11 socket, some other
      source callback (the drm fd or a wayland client socket) can cause somebody
      to do an X roundtrip (DRI2 get buffers, for example) and queue up events
      in the xcb buffer.  When we get back to epoll, the X fd no longer polls
      readable and we don't process those events until we get another X event.
      The check callback is called after a round of dispatching and lets a source
      check if it has data to dispatch and mark itself ready.  Next round of
      dispatching will then process it immediately instead of blocking in
  17. 20 Apr, 2011 1 commit
  18. 11 Apr, 2011 1 commit
  19. 16 Mar, 2011 1 commit
  20. 19 Jan, 2011 1 commit
  21. 05 Jan, 2011 1 commit
  22. 08 Dec, 2010 3 commits
  23. 07 Dec, 2010 5 commits
  24. 06 Dec, 2010 1 commit