aboutsummaryrefslogtreecommitdiffstats
path: root/protocol
Commit message (Collapse)AuthorAgeFilesLines
* Fix distcheck where protocol.xsl was missing in the tarballGaetan Nadon2012-03-042-2/+4
| | | | | | | To reproduce, invoke distcheck from an out-of-source tree. Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
* protocol: Clarify the documentation for the fullscreen protocolRob Bradford2012-02-291-19/+34
|
* protocol: fix make distcheckPeter Hutterer2012-02-291-3/+4
| | | | | | | Distribute all source files that we need for buildling. Plus, remove the html file on make clean. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* protocol.xsl: Rename stylesheet to wayland-protocol.cssKristian Høgsberg2012-02-233-2/+2
| | | | Otherwise it clashes with the website stylesheet.
* protocol: add xslt stylesheet to prettify the protocolPeter Hutterer2012-02-233-0/+252
| | | | | | Includes rudimentary styling only. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* protocol: fix missing hyphenation for "client-created"Peter Hutterer2012-02-231-1/+1
| | | | Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
* Add wl_region and surface requests to set opaque and input regionsKristian Høgsberg2012-02-231-0/+76
|
* Split pointer_focus and keyboard_focus into enter and leave eventsKristian Høgsberg2012-02-231-3/+15
|
* protocol: remove absolute coordinates from pointerPekka Paalanen2012-02-161-7/+2
| | | | | | | | | | Remove the absolute coordinate fields from the pointer motion and pointer_focus events. Clients are not supposed to see any global coordinates. Fix wayland-server code accordingly. wayland-client code is unaffected. Signed-off-by: Pekka Paalanen <ppaalanen@gmail.com>
* data_device: get rid of attach requestAnder Conselvan de Oliveira2012-02-161-8/+14
| | | | | | | | | In the effort to make everything a regular surface, remove data_device.attach request. To maintan the functionality, add an icon surface parameter to data_device.start_drag. Signed-off-by: Kristian Høgsberg <krh@bitplanet.net> Signed-off-by: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com>
* Add fullscreen protocolJuan Zhao2012-02-161-7/+31
| | | | | | | | | | | | | | | | | | | | | | | | | Map the surface as a fullscreen surface. On the output the surface is assigned to. The client can use different fulllscreen method to fix the size mismatch issue: default, scale, driver and fill. Hints to indicate compositor how to deal with this fullscreen surface. "default" means the client has no preference on fullscreen behavior, policies are determined by compositor. "scale" means the client prefers scaling by the compositor. Scaling would always preserve surface's aspect ratio. And the surface is centered. "driver" means the client wants to switch video mode to the smallest mode that can fit the client buffer. If the sizes do not match, black borders are added. And the framerate parameter is used for "driver" method, to indicate the preferred framerate. framerate=0 means that the app does not care about framerate "fill" means the client wants to add blackborders to the surface. This would be preferring 1:1 pixel mapping in the monitor native video mode. The surface is centered.
* Add maximized protocolJuan Zhao2012-02-161-0/+13
| | | | | | | | | | | A request from the client to ask the compositor to maximize the surface. The compositor will reply with a configure event telling the expected new surface size. The operation is completed on the next buffer attach to this surface. A maximized client will fill the fullscreen of the output it is bound to, except the panel area. This is the main difference between a maximized shell surface and a fullscreen shell surface.
* protocol: fix typoTiago Vignatti2012-02-091-5/+5
| | | | Signed-off-by: Tiago Vignatti <tiago.vignatti@intel.com>
* scanner: allow summary attributes in args and <description> in <protocol>Jesse Barnes2012-01-191-1/+3
| | | | | Add support for arg summaries for use by detailed structure element descriptions.
* protocol: Convert comments to new documentation tagsKristian Høgsberg2012-01-181-173/+285
|
* scanner: Support documentation elementsJesse Barnes2012-01-181-3/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On Wed, 18 Jan 2012 12:29:37 -0800 "Kristensen, Kristian H" <kristian.h.kristensen@intel.com> wrote: > Yeah, that looks good. I was thinking of a separate <description> tag > to avoid stuffing too much into an attribute. How does this look? It adds a summary attribute to atomic elements, and a <description> tag with a summary for others. Spits out enum documentation like this: /** * wl_display_error - global error values * @WL_DISPLAY_ERROR_INVALID_OBJECT: server couldn't find object * @WL_DISPLAY_ERROR_INVALID_METHOD: method doesn't exist on the specified interface * @WL_DISPLAY_ERROR_NO_MEMORY: server is out of memory * * These errors are global and can be emitted in response to any server request. */ enum wl_display_error { WL_DISPLAY_ERROR_INVALID_OBJECT = 0, WL_DISPLAY_ERROR_INVALID_METHOD = 1, WL_DISPLAY_ERROR_NO_MEMORY = 2, }; and structure documentation like this: /** * wl_display - core global object * @bind: bind an object to the display * @sync: (none) * * The core global object. This is a special singleton object. It is used for * internal wayland protocol features. */ struct wl_display_interface { void (*bind)(struct wl_client *client, struct wl_resource *resource, uint32_t name, const char *interface, uint32_t version, uint32_t id); void (*sync)(struct wl_client *client, struct wl_resource *resource, uint32_t callback); };
* shm: Drop non-premul format, use less ambiguous ARGB8888 naming conventionKristian Høgsberg2012-01-111-3/+2
| | | | This also matches the new wl_drm format names.
* Add new wl_shell popup surface typeKristian Høgsberg2012-01-061-0/+26
|
* protocol: update touch_down with focus surfaceTiago Vignatti2011-12-211-0/+1
| | | | Signed-off-by: Tiago Vignatti <tiago.vignatti@intel.com>
* protocol: Add a bit of documentationKristian Høgsberg2011-12-191-0/+16
|
* protocol: introduce wl_shell_surfacePekka Paalanen2011-11-291-11/+15
| | | | | | | | | | | | | | | | | | | Requests like 'move' and 'set_toplevel' are really methods of a surface, not methods of a global shell object. Move all these methods to a new interface, wl_shell_surface. The global object wl_shell will contain only 'get_shell_surface' request, which creates and associates a wl_shell_surface object to a given wl_surface object. This will also give the shell plugin (if you look at the demo compositor) means to store per-surface private data in a natural way. Due to a limitation in delete_id event handling on client side, the client must destroy its wl_shell_surface object before destroying the wl_surface object. Otherwise it may just leak an id. Signed-off-by: Pekka Paalanen <ppaalanen@gmail.com>
* New drag and drop / selection protocolKristian Høgsberg2011-11-231-147/+109
| | | | | | | | | | | 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.
* Add display event to acknowledge ID deletionKristian Høgsberg2011-11-171-0/+4
| | | | | | | We need to make sure the client doesn't reuse an object ID until the server has seen the destroy request. When a client destroys an ID the server will now respond with the display.delete_id event, which lets the client block reuse until it receives the event.
* protocol: Change global_remove arg to be 'name' insteadl of 'id'Kristian Høgsberg2011-10-241-1/+1
| | | | Consistent with global args.
* scanner: Catch more invalid attribute combinations for argKristian Høgsberg2011-10-241-1/+1
| | | | Spotted by Jakob Bornecrantz.
* Remove the wl_visual interfaceKristian Høgsberg2011-08-311-20/+13
| | | | | | | | | | | | | | | | | | 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.
* Remove range protocolKristian Høgsberg2011-08-271-8/+0
|
* Always allocate a new wl_resource when binding an objectKristian Høgsberg2011-08-271-3/+3
| | | | Previously we would bind some resources into multiple client hash tables.
* Bind globals to client provided object IDsKristian Høgsberg2011-08-271-1/+2
|
* Use a callback object instead of ad-hoc lists for sync and frame eventsKristian Høgsberg2011-08-271-18/+13
| | | | | | | | | So obvious in retrospect. The object system can do all the work for us and keep track of pending calls as regular objects and we don't need to abuse the resource system to get them cleaned up on client exit. We don't need the custom key management or (broken) lookup, we just sue object IDs. And last but not least, anybody can receive the callback, not just display listeners.
* protocol: Delete screenshooter.xmlTiago Vignatti2011-07-261-7/+0
| | | | | | The protocol interface is on compositor's side now. Signed-off-by: Tiago Vignatti <tiago.vignatti@intel.com>
* scanner: Take copyright notice from xml fileKristian Høgsberg2011-07-251-0/+26
|
* protocol: fix key event and related commentsTiago Vignatti2011-07-151-3/+3
|
* protocol: Fix type of visual arg in token_visual eventKristian Høgsberg2011-07-151-1/+1
|
* protocol: Make id arg of display.global event be just a uintKristian Høgsberg2011-07-111-1/+1
| | | | Global names are different from object IDs.
* Add touch events to protocol.Laszlo Agocs2011-06-291-0/+27
|
* Merge remote-tracking branch 'bnf/buffer.release'Kristian Høgsberg2011-06-211-0/+3
|\
| * Add buffer.release eventBenjamin Franzke2011-06-211-0/+3
| |
* | Add more protocol for communicating screen geometryKristian Høgsberg2011-06-211-1/+26
| |
* | Add wl_display_remove_global.Laszlo Agocs2011-06-201-0/+5
|/ | | | | | | | Change 4453ba084aae5a00318b9dfdeda95e8eaa17494c 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.
* Move map functionality into shellKristian Høgsberg2011-06-181-28/+33
| | | | | | Initial surface.attach makes the surface visible and clients can set the surface type using shell.set_transient etc or other interfaces prior to that.
* Add event to associate visuals with a pixel format tokenKristian Høgsberg2011-05-121-0/+11
|
* Define shm specific errorsKristian Høgsberg2011-05-111-0/+6
| | | | We stop abusing the wl_display error codes for shm purposes.
* Unify error eventsKristian Høgsberg2011-05-111-14/+10
| | | | | Consolidate the different error events into one. This event will also be usable for other interaces.
* Add buffer.damage request to the protocolBenjamin Franzke2011-04-221-8/+18
| | | | Thus remove the server-side used vfunc buffer::damage.
* scanner: Don't hardcode the wl_ prefix in the code generatorKristian Høgsberg2011-04-201-35/+35
|
* Introduce display.bind to request events from a globalKristian Høgsberg2011-04-181-0/+6
|
* Extent frame event to be surface dependentBenjamin Franzke2011-03-161-0/+1
|
* protocol/wayland: Drop drm interface (move into mesa)Benjamin Franzke2011-02-281-36/+0
|
* Add initial basic support for fullscreen surfacesKristian Høgsberg2011-01-281-0/+10
|