Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
/*
|
|
|
|
|
* Copyright © 2008-2011 Kristian Høgsberg
|
|
|
|
|
* Copyright © 2012 Collabora, Ltd.
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
*
|
|
|
|
|
* Permission to use, copy, modify, distribute, and sell this software and
|
|
|
|
|
* its documentation for any purpose is hereby granted without fee, provided
|
|
|
|
|
* that the above copyright notice appear in all copies and that both that
|
|
|
|
|
* copyright notice and this permission notice appear in supporting
|
|
|
|
|
* documentation, and that the name of the copyright holders not be used in
|
|
|
|
|
* advertising or publicity pertaining to distribution of the software
|
|
|
|
|
* without specific, written prior permission. The copyright holders make
|
|
|
|
|
* no representations about the suitability of this software for any
|
|
|
|
|
* purpose. It is provided "as is" without express or implied warranty.
|
|
|
|
|
*
|
|
|
|
|
* THE COPYRIGHT HOLDERS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS
|
|
|
|
|
* SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
|
|
|
|
|
* FITNESS, IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY
|
|
|
|
|
* SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER
|
|
|
|
|
* RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
|
|
|
|
|
* CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
|
|
|
|
|
* CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef _WAYLAND_SYSTEM_COMPOSITOR_H_
|
|
|
|
|
#define _WAYLAND_SYSTEM_COMPOSITOR_H_
|
|
|
|
|
|
|
|
|
|
#include <libudev.h>
|
|
|
|
|
#include <pixman.h>
|
|
|
|
|
#include <wayland-server.h>
|
|
|
|
|
|
|
|
|
|
#include <GLES2/gl2.h>
|
|
|
|
|
#include <GLES2/gl2ext.h>
|
|
|
|
|
#include <EGL/egl.h>
|
|
|
|
|
#include <EGL/eglext.h>
|
|
|
|
|
|
|
|
|
|
#include "matrix.h"
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
|
|
|
|
|
struct weston_transform {
|
|
|
|
|
struct weston_matrix matrix;
|
|
|
|
|
struct wl_list link;
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct weston_surface;
|
|
|
|
|
struct weston_input_device;
|
|
|
|
|
|
|
|
|
|
struct weston_mode {
|
|
|
|
|
uint32_t flags;
|
|
|
|
|
int32_t width, height;
|
|
|
|
|
uint32_t refresh;
|
|
|
|
|
struct wl_list link;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct weston_output {
|
|
|
|
|
struct wl_list link;
|
|
|
|
|
struct weston_compositor *compositor;
|
|
|
|
|
struct weston_matrix matrix;
|
|
|
|
|
struct wl_list frame_callback_list;
|
|
|
|
|
int32_t x, y, mm_width, mm_height;
|
|
|
|
|
pixman_region32_t region;
|
|
|
|
|
pixman_region32_t previous_damage;
|
|
|
|
|
uint32_t flags;
|
|
|
|
|
int repaint_needed;
|
|
|
|
|
int repaint_scheduled;
|
|
|
|
|
|
|
|
|
|
char *make, *model;
|
|
|
|
|
uint32_t subpixel;
|
|
|
|
|
|
|
|
|
|
struct weston_mode *current;
|
|
|
|
|
struct wl_list mode_list;
|
|
|
|
|
|
|
|
|
|
void (*repaint)(struct weston_output *output);
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
int (*set_hardware_cursor)(struct weston_output *output,
|
|
|
|
|
struct weston_input_device *input);
|
|
|
|
|
void (*destroy)(struct weston_output *output);
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct weston_input_device {
|
|
|
|
|
struct wl_input_device input_device;
|
|
|
|
|
struct weston_compositor *compositor;
|
|
|
|
|
struct weston_surface *sprite;
|
|
|
|
|
int32_t hotspot_x, hotspot_y;
|
|
|
|
|
struct wl_list link;
|
|
|
|
|
uint32_t modifier_state;
|
|
|
|
|
int hw_cursor;
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
|
|
|
|
|
uint32_t num_tp;
|
|
|
|
|
struct wl_surface *touch_focus;
|
|
|
|
|
struct wl_listener touch_focus_listener;
|
|
|
|
|
struct wl_resource *touch_focus_resource;
|
|
|
|
|
struct wl_listener touch_focus_resource_listener;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum weston_visual {
|
|
|
|
|
WESTON_NONE_VISUAL,
|
|
|
|
|
WESTON_ARGB_VISUAL,
|
|
|
|
|
WESTON_RGB_VISUAL
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct weston_shader {
|
|
|
|
|
GLuint program;
|
|
|
|
|
GLuint vertex_shader, fragment_shader;
|
compositor: fix and simplify shader uniform handling
The uniform location variables should be signed, according to the OpenGL
ES 2 specification. Moreover, GL_NONE, i.e. 0, is not an invalid nor
special location; it is actually used as a valid uniform location.
Change struct weston_shader uniform members to signed.
Stop using 0 for identifying a non-existing uniform, use -1 instead.
Furthermore, as the spec says a) glGetUniformLocation() will return -1
for non-active/existing uniforms, and b) glUniform*() function will
simply ignore all calls with location -1, we can simplify the code. We
don't have to avoid locating uniforms that don't exist, and we don't
need to test for them in weston_surface_draw() either.
Remove the micro-optimisation that avoids setting 'alpha' uniform if it
has not changed, in the name of simplification.
Unify shader creation by dropping init_solid_shader(), and calling
weston_shader_init() instead. The downside is that we compile the vertex
shader twice at startup now.
Signed-off-by: Pekka Paalanen <ppaalanen@gmail.com>
13 years ago
|
|
|
GLint proj_uniform;
|
|
|
|
|
GLint tex_uniform;
|
|
|
|
|
GLint alpha_uniform;
|
|
|
|
|
GLint color_uniform;
|
|
|
|
|
GLint texwidth_uniform;
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct weston_animation {
|
|
|
|
|
void (*frame)(struct weston_animation *animation,
|
|
|
|
|
struct weston_output *output, uint32_t msecs);
|
|
|
|
|
struct wl_list link;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct weston_spring {
|
|
|
|
|
double k;
|
|
|
|
|
double friction;
|
|
|
|
|
double current;
|
|
|
|
|
double target;
|
|
|
|
|
double previous;
|
|
|
|
|
uint32_t timestamp;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct weston_shell {
|
|
|
|
|
void (*lock)(struct weston_shell *shell);
|
|
|
|
|
void (*unlock)(struct weston_shell *shell);
|
|
|
|
|
void (*map)(struct weston_shell *shell, struct weston_surface *surface,
|
|
|
|
|
int32_t width, int32_t height);
|
|
|
|
|
void (*configure)(struct weston_shell *shell,
|
|
|
|
|
struct weston_surface *surface,
|
|
|
|
|
GLfloat x, GLfloat y, int32_t width, int32_t height);
|
|
|
|
|
void (*destroy)(struct weston_shell *shell);
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum {
|
|
|
|
|
WESTON_COMPOSITOR_ACTIVE,
|
|
|
|
|
WESTON_COMPOSITOR_IDLE, /* shell->unlock called on activity */
|
|
|
|
|
WESTON_COMPOSITOR_SLEEPING /* no rendering, no frame events */
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct screenshooter;
|
|
|
|
|
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
struct weston_compositor {
|
|
|
|
|
struct wl_shm *shm;
|
|
|
|
|
struct weston_xserver *wxs;
|
|
|
|
|
|
|
|
|
|
EGLDisplay display;
|
|
|
|
|
EGLContext context;
|
|
|
|
|
EGLConfig config;
|
|
|
|
|
GLuint fbo;
|
|
|
|
|
struct weston_shader texture_shader;
|
|
|
|
|
struct weston_shader solid_shader;
|
|
|
|
|
struct weston_shader *current_shader;
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
struct wl_display *wl_display;
|
|
|
|
|
|
|
|
|
|
struct weston_shell *shell;
|
|
|
|
|
|
|
|
|
|
/* There can be more than one, but not right now... */
|
|
|
|
|
struct wl_input_device *input_device;
|
|
|
|
|
|
|
|
|
|
struct wl_list output_list;
|
|
|
|
|
struct wl_list input_device_list;
|
|
|
|
|
struct wl_list surface_list;
|
|
|
|
|
struct wl_list binding_list;
|
|
|
|
|
struct wl_list animation_list;
|
|
|
|
|
struct {
|
|
|
|
|
struct weston_spring spring;
|
|
|
|
|
struct weston_animation animation;
|
|
|
|
|
struct weston_surface *surface;
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
} fade;
|
|
|
|
|
|
|
|
|
|
uint32_t state;
|
|
|
|
|
struct wl_event_source *idle_source;
|
|
|
|
|
uint32_t idle_inhibit;
|
|
|
|
|
int option_idle_time; /* default timeout, s */
|
|
|
|
|
int idle_time; /* effective timeout, s */
|
|
|
|
|
|
|
|
|
|
/* Repaint state. */
|
|
|
|
|
struct timespec previous_swap;
|
|
|
|
|
struct wl_array vertices, indices;
|
|
|
|
|
|
|
|
|
|
struct weston_surface *overlay;
|
|
|
|
|
struct weston_switcher *switcher;
|
|
|
|
|
uint32_t focus;
|
|
|
|
|
|
|
|
|
|
PFNGLEGLIMAGETARGETRENDERBUFFERSTORAGEOESPROC
|
|
|
|
|
image_target_renderbuffer_storage;
|
|
|
|
|
PFNGLEGLIMAGETARGETTEXTURE2DOESPROC image_target_texture_2d;
|
|
|
|
|
PFNEGLCREATEIMAGEKHRPROC create_image;
|
|
|
|
|
PFNEGLDESTROYIMAGEKHRPROC destroy_image;
|
|
|
|
|
PFNEGLBINDWAYLANDDISPLAYWL bind_display;
|
|
|
|
|
PFNEGLUNBINDWAYLANDDISPLAYWL unbind_display;
|
|
|
|
|
int has_bind_display;
|
|
|
|
|
|
|
|
|
|
void (*destroy)(struct weston_compositor *ec);
|
|
|
|
|
int (*authenticate)(struct weston_compositor *c, uint32_t id);
|
|
|
|
|
EGLImageKHR (*create_cursor_image)(struct weston_compositor *c,
|
|
|
|
|
int32_t *width, int32_t *height);
|
|
|
|
|
|
|
|
|
|
struct screenshooter *screenshooter;
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
};
|
|
|
|
|
|
|
|
|
|
#define MODIFIER_CTRL (1 << 8)
|
|
|
|
|
#define MODIFIER_ALT (1 << 9)
|
|
|
|
|
#define MODIFIER_SUPER (1 << 10)
|
|
|
|
|
|
|
|
|
|
enum weston_output_flags {
|
|
|
|
|
WL_OUTPUT_FLIPPED = 0x01
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct weston_surface {
|
|
|
|
|
struct wl_surface surface;
|
|
|
|
|
struct weston_compositor *compositor;
|
|
|
|
|
GLuint texture;
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
pixman_region32_t damage;
|
|
|
|
|
pixman_region32_t opaque;
|
|
|
|
|
int32_t pitch;
|
|
|
|
|
struct wl_list link;
|
|
|
|
|
struct wl_list buffer_link;
|
|
|
|
|
struct weston_shader *shader;
|
|
|
|
|
GLfloat color[4];
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
uint32_t alpha;
|
|
|
|
|
uint32_t visual;
|
|
|
|
|
int overlapped;
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
|
|
|
|
|
/* Surface geometry state, mutable.
|
|
|
|
|
* If you change anything, set dirty = 1.
|
|
|
|
|
* That includes the transformations referenced from the list.
|
|
|
|
|
*/
|
|
|
|
|
struct {
|
|
|
|
|
GLfloat x, y; /* surface translation on display */
|
|
|
|
|
int32_t width, height;
|
|
|
|
|
|
|
|
|
|
/* struct weston_transform */
|
|
|
|
|
struct wl_list transformation_list;
|
|
|
|
|
|
|
|
|
|
int dirty;
|
|
|
|
|
} geometry;
|
|
|
|
|
|
|
|
|
|
/* State derived from geometry state, read-only.
|
|
|
|
|
* This is updated by weston_surface_update_transform().
|
|
|
|
|
*/
|
|
|
|
|
struct {
|
|
|
|
|
pixman_region32_t boundingbox;
|
|
|
|
|
|
|
|
|
|
/* matrix and inverse are used only if enabled = 1.
|
|
|
|
|
* If enabled = 0, use x, y, width, height directly.
|
|
|
|
|
*/
|
|
|
|
|
int enabled;
|
|
|
|
|
struct weston_matrix matrix;
|
|
|
|
|
struct weston_matrix inverse;
|
|
|
|
|
|
|
|
|
|
struct weston_transform position; /* matrix from x, y */
|
|
|
|
|
} transform;
|
|
|
|
|
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
/*
|
|
|
|
|
* Which output to vsync this surface to.
|
|
|
|
|
* Used to determine, whether to send or queue frame events.
|
|
|
|
|
* Must be NULL, if 'link' is not in weston_compositor::surface_list.
|
|
|
|
|
*/
|
|
|
|
|
struct weston_output *output;
|
|
|
|
|
|
|
|
|
|
struct weston_output *fullscreen_output;
|
|
|
|
|
struct wl_list frame_callback_list;
|
|
|
|
|
|
|
|
|
|
EGLImageKHR image;
|
|
|
|
|
|
|
|
|
|
struct wl_buffer *buffer;
|
|
|
|
|
struct wl_listener buffer_destroy_listener;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_surface_update_transform(struct weston_surface *surface);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_surface_to_global(struct weston_surface *surface,
|
|
|
|
|
int32_t sx, int32_t sy, int32_t *x, int32_t *y);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_surface_from_global(struct weston_surface *surface,
|
|
|
|
|
int32_t x, int32_t y, int32_t *sx, int32_t *sy);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_device_repick(struct wl_input_device *device, uint32_t time);
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_spring_init(struct weston_spring *spring,
|
|
|
|
|
double k, double current, double target);
|
|
|
|
|
void
|
|
|
|
|
weston_spring_update(struct weston_spring *spring, uint32_t msec);
|
|
|
|
|
int
|
|
|
|
|
weston_spring_done(struct weston_spring *spring);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_surface_activate(struct weston_surface *surface,
|
|
|
|
|
struct weston_input_device *device, uint32_t time);
|
|
|
|
|
void
|
|
|
|
|
weston_surface_draw(struct weston_surface *es, struct weston_output *output);
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
|
|
|
|
|
void
|
|
|
|
|
notify_motion(struct wl_input_device *device,
|
|
|
|
|
uint32_t time, int x, int y);
|
|
|
|
|
void
|
|
|
|
|
notify_button(struct wl_input_device *device,
|
|
|
|
|
uint32_t time, int32_t button, int32_t state);
|
|
|
|
|
void
|
|
|
|
|
notify_key(struct wl_input_device *device,
|
|
|
|
|
uint32_t time, uint32_t key, uint32_t state);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
notify_pointer_focus(struct wl_input_device *device,
|
|
|
|
|
uint32_t time,
|
|
|
|
|
struct weston_output *output,
|
|
|
|
|
int32_t x, int32_t y);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
notify_keyboard_focus(struct wl_input_device *device,
|
|
|
|
|
uint32_t time, struct weston_output *output,
|
|
|
|
|
struct wl_array *keys);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
notify_touch(struct wl_input_device *device, uint32_t time, int touch_id,
|
|
|
|
|
int x, int y, int touch_type);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_output_finish_frame(struct weston_output *output, int msecs);
|
|
|
|
|
void
|
|
|
|
|
weston_output_damage(struct weston_output *output);
|
|
|
|
|
struct weston_surface *
|
|
|
|
|
weston_compositor_pick_surface(struct weston_compositor *compositor,
|
|
|
|
|
int32_t x, int32_t y, int32_t *sx, int32_t *sy);
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
void
|
|
|
|
|
weston_compositor_repick(struct weston_compositor *compositor);
|
|
|
|
|
void
|
|
|
|
|
weston_compositor_schedule_repaint(struct weston_compositor *compositor);
|
|
|
|
|
void
|
|
|
|
|
weston_compositor_fade(struct weston_compositor *compositor, float tint);
|
|
|
|
|
void
|
|
|
|
|
weston_compositor_damage_all(struct weston_compositor *compositor);
|
|
|
|
|
void
|
|
|
|
|
weston_compositor_unlock(struct weston_compositor *compositor);
|
|
|
|
|
void
|
|
|
|
|
weston_compositor_wake(struct weston_compositor *compositor);
|
|
|
|
|
void
|
|
|
|
|
weston_compositor_activity(struct weston_compositor *compositor);
|
|
|
|
|
|
|
|
|
|
struct weston_binding;
|
|
|
|
|
typedef void (*weston_binding_handler_t)(struct wl_input_device *device,
|
|
|
|
|
uint32_t time, uint32_t key,
|
|
|
|
|
uint32_t button,
|
|
|
|
|
uint32_t state, void *data);
|
|
|
|
|
struct weston_binding *
|
|
|
|
|
weston_compositor_add_binding(struct weston_compositor *compositor,
|
|
|
|
|
uint32_t key, uint32_t button, uint32_t modifier,
|
|
|
|
|
weston_binding_handler_t binding, void *data);
|
|
|
|
|
void
|
|
|
|
|
weston_binding_destroy(struct weston_binding *binding);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_binding_list_destroy_all(struct wl_list *list);
|
|
|
|
|
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
void
|
|
|
|
|
weston_compositor_run_binding(struct weston_compositor *compositor,
|
|
|
|
|
struct weston_input_device *device,
|
|
|
|
|
uint32_t time,
|
|
|
|
|
uint32_t key, uint32_t button, int32_t state);
|
|
|
|
|
struct wl_list *
|
|
|
|
|
weston_compositor_top(struct weston_compositor *compositor);
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
|
|
|
|
|
struct weston_surface *
|
|
|
|
|
weston_surface_create(struct weston_compositor *compositor);
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_surface_configure(struct weston_surface *surface,
|
|
|
|
|
GLfloat x, GLfloat y, int width, int height);
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_surface_assign_output(struct weston_surface *surface);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_surface_damage(struct weston_surface *surface);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_surface_damage_below(struct weston_surface *surface);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_surface_damage_rectangle(struct weston_surface *surface,
|
|
|
|
|
int32_t x, int32_t y,
|
|
|
|
|
int32_t width, int32_t height);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_buffer_post_release(struct wl_buffer *buffer);
|
|
|
|
|
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
uint32_t
|
|
|
|
|
weston_compositor_get_time(void);
|
|
|
|
|
|
|
|
|
|
int
|
|
|
|
|
weston_compositor_init(struct weston_compositor *ec, struct wl_display *display);
|
|
|
|
|
void
|
|
|
|
|
weston_compositor_shutdown(struct weston_compositor *ec);
|
|
|
|
|
void
|
|
|
|
|
weston_output_move(struct weston_output *output, int x, int y);
|
|
|
|
|
void
|
|
|
|
|
weston_output_init(struct weston_output *output, struct weston_compositor *c,
|
|
|
|
|
int x, int y, int width, int height, uint32_t flags);
|
|
|
|
|
void
|
|
|
|
|
weston_output_destroy(struct weston_output *output);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_input_device_init(struct weston_input_device *device,
|
|
|
|
|
struct weston_compositor *ec);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_input_device_release(struct weston_input_device *device);
|
|
|
|
|
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
void
|
|
|
|
|
weston_switcher_init(struct weston_compositor *compositor);
|
|
|
|
|
|
|
|
|
|
enum {
|
|
|
|
|
TTY_ENTER_VT,
|
|
|
|
|
TTY_LEAVE_VT
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
typedef void (*tty_vt_func_t)(struct weston_compositor *compositor, int event);
|
|
|
|
|
|
|
|
|
|
struct tty *
|
|
|
|
|
tty_create(struct weston_compositor *compositor,
|
|
|
|
|
tty_vt_func_t vt_func, int tty_nr);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
tty_destroy(struct tty *tty);
|
|
|
|
|
|
|
|
|
|
struct screenshooter *
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
screenshooter_create(struct weston_compositor *ec);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
screenshooter_destroy(struct screenshooter *s);
|
|
|
|
|
|
Rename wayland-compositor to weston
This rename addresses a few problems around the split between core
Wayland and the wayland-demos repository.
1) Initially, we had one big repository with protocol code, sample
compositor and sample clients. We split that repository to make it
possible to implement the protocol without pulling in the sample/demo
code. At this point, the compositor is more than just a "demo" and
wayland-demos doesn't send the right message. The sample compositor
is a useful, self-contained project in it's own right, and we want to
move away from the "demos" label.
2) Another problem is that the wayland-demos compositor is often
called "the wayland compsitor", but it's really just one possible
compositor. Existing X11 compositors are expected to add Wayland
support and then gradually phase out/modularize the X11 support, for
example. Conversely, it's hard to talk about the wayland-demos
compositor specifically as opposed to, eg, the wayland protocol or a
wayland compositor in general.
We are also renaming the repo to weston, and the compositor
subdirectory to src/, to emphasize that the main "output" is the
compositor.
13 years ago
|
|
|
uint32_t *
|
|
|
|
|
weston_load_image(const char *filename,
|
|
|
|
|
int32_t *width_arg, int32_t *height_arg,
|
|
|
|
|
uint32_t *stride_arg);
|
|
|
|
|
|
|
|
|
|
struct weston_process;
|
|
|
|
|
typedef void (*weston_process_cleanup_func_t)(struct weston_process *process,
|
|
|
|
|
int status);
|
|
|
|
|
|
|
|
|
|
struct weston_process {
|
|
|
|
|
pid_t pid;
|
|
|
|
|
weston_process_cleanup_func_t cleanup;
|
|
|
|
|
struct wl_list link;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct wl_client *
|
|
|
|
|
weston_client_launch(struct weston_compositor *compositor,
|
|
|
|
|
struct weston_process *proc,
|
|
|
|
|
const char *path,
|
|
|
|
|
weston_process_cleanup_func_t cleanup);
|
|
|
|
|
|
|
|
|
|
void
|
|
|
|
|
weston_watch_process(struct weston_process *process);
|
|
|
|
|
|
|
|
|
|
int
|
|
|
|
|
weston_xserver_init(struct weston_compositor *compositor);
|
|
|
|
|
void
|
|
|
|
|
weston_xserver_destroy(struct weston_compositor *compositor);
|
|
|
|
|
void
|
|
|
|
|
weston_xserver_surface_activate(struct weston_surface *surface);
|
|
|
|
|
void
|
|
|
|
|
weston_xserver_set_selection(struct weston_input_device *device);
|
|
|
|
|
|
|
|
|
|
struct weston_zoom;
|
|
|
|
|
typedef void (*weston_zoom_done_func_t)(struct weston_zoom *zoom, void *data);
|
|
|
|
|
|
|
|
|
|
struct weston_zoom *
|
|
|
|
|
weston_zoom_run(struct weston_surface *surface, GLfloat start, GLfloat stop,
|
|
|
|
|
weston_zoom_done_func_t done, void *data);
|
|
|
|
|
|
|
|
|
|
#endif
|