On Tue, Jan 8, 2013 at 9:14 PM, Vasily Khoruzhick wrote:
> On Tue, Jan 8, 2013 at 10:50 PM, John Kåre Alsaker
> wrote:
>
> Hi John,
>
>> I'd like for output_create, output_destroy, renderer_destroy,
>> set_border and repaint_output to be virtual functions as part of a new
>> abstraction which is
On Tue, Jan 8, 2013 at 10:50 PM, John Kåre Alsaker
wrote:
Hi John,
> I'd like for output_create, output_destroy, renderer_destroy,
> set_border and repaint_output to be virtual functions as part of a new
> abstraction which is responsible for handling buffers and renderers
> for the backends. Th
I'd like for output_create, output_destroy, renderer_destroy,
set_border and repaint_output to be virtual functions as part of a new
abstraction which is responsible for handling buffers and renderers
for the backends. These may simply be new fields in weston_renderer
that the backends override as
On Tue, Jan 8, 2013 at 1:36 PM, John Kåre Alsaker
wrote:
> I'd like to see this callback in a buffer manager abstraction which
> could encapsulate EGL and X11/fb/kms buffer management and get rid of
> duplicated code for the renderers. However if it's added to
> weston_renderer, it should be destr
I'd like to see this callback in a buffer manager abstraction which
could encapsulate EGL and X11/fb/kms buffer management and get rid of
duplicated code for the renderers. However if it's added to
weston_renderer, it should be destroyed by the compositor and not by
the backends.
On Tue, Jan 8, 20
Signed-off-by: Vasily Khoruzhick
---
src/compositor-android.c | 6 +++---
src/compositor-drm.c | 4 ++--
src/compositor-headless.c | 2 +-
src/compositor-rpi.c | 4 ++--
src/compositor-wayland.c | 4 ++--
src/compositor-x11.c | 10 ++
src/compositor.h | 3 +
