Go to file
Alexander Larsson b693088904 protocol: Modes are specified in HW pixels
Modes are mainly meant to be used in coordination with fullscreen in
DRIVER mode, by e.g. games. For such games what they generally want
is to match some hardware mode and resize their window for that. We
don't really need to complicate this with the scaling. So, we
keep the resolutions in HW pixels, and drop the SCALED flag (as it
is now useless).

This lets you just create e.g an 800x600 buffer of scale 1 and
fullscreen that, ignoring the output scaling factor (although you can
of course also respect it and create a 400x300 surface at scale 2).
Conceptually the mode change is treated like a scaling which overrides
the normal output scale.

The only complexity is the FILL mode where it can happen that the user
specifies a buffer of the same size as the screen, but the output has scale
2 and the buffer scale 1. Just scanning out this buffer will work, but
effectively this is a downscaling operation, as the "real" size of the surface
in pels is twice the size of the output. We solve this by allowing FILL to
downscale (but still not upscale).
2013-05-28 15:40:02 -04:00
cursor pkgconfig: Use configure provided directories 2012-11-27 20:35:50 -05:00
doc protocol: Fix documentation typo 2013-05-22 15:49:13 -04:00
m4 Clean up .gitignore files 2010-11-11 20:11:27 -05:00
protocol protocol: Modes are specified in HW pixels 2013-05-28 15:40:02 -04:00
spec doc: move documentation from the tex file to docbook 2012-03-28 23:04:25 -04:00
src server: Drop struct wl_surface 2013-05-08 09:45:59 -04:00
tests Change wl_closure_invoke to take an opcode instead of an actual function pointer 2013-03-18 23:04:32 -04:00
.gitignore gitignore: add test-suite files 2013-01-24 16:14:52 -05:00
autogen.sh Update autotools configuration 2010-11-06 21:04:03 -04:00
configure.ac configure.ac: Bump to 1.1.90 to open master for 1.2 work 2013-04-29 16:42:40 -04:00
COPYING Add COPYING 2012-04-25 10:12:21 -04:00
Makefile.am Fix distcheck by adding back protocol/Makefile.am 2012-11-19 17:11:58 -05:00
README README: Fix typos 2013-02-14 12:14:54 -05:00
TODO Update TODO 2012-10-21 20:53:37 -04:00
wayland-scanner.m4.in Split into a core repository that only holds the core Wayland libraries 2011-02-14 22:21:13 -05:00
wayland-scanner.mk Split into a core repository that only holds the core Wayland libraries 2011-02-14 22:21:13 -05:00

What is Wayland

Wayland is a project to define a protocol for a compositor to talk to
its clients as well as a library implementation of the protocol.  The
compositor can be a standalone display server running on Linux kernel
modesetting and evdev input devices, an X application, or a wayland
client itself.  The clients can be traditional applications, X servers
(rootless or fullscreen) or other display servers.

The wayland protocol is essentially only about input handling and
buffer management.  The compositor receives input events and forwards
them to the relevant client.  The clients creates buffers and renders
into them and notifies the compositor when it needs to redraw.  The
protocol also handles drag and drop, selections, window management and
other interactions that must go through the compositor.  However, the
protocol does not handle rendering, which is one of the features that
makes wayland so simple.  All clients are expected to handle rendering
themselves, typically through cairo or OpenGL.

The weston compositor is a reference implementation of a wayland
compositor and the weston repository also includes a few example
clients.

Building the wayland libraries is fairly simple, aside from libffi,
they don't have many dependencies:

    $ git clone git://anongit.freedesktop.org/wayland/wayland
    $ cd wayland
    $ ./autogen.sh --prefix=PREFIX
    $ make
    $ make install

where PREFIX is where you want to install the libraries.  See
http://wayland.freedesktop.org for more complete build instructions
for wayland, weston, xwayland and various toolkits.