pointers in E now come in two flavors, one for each protocol that we currently support. each is created from the owner compositor backend:
X pointers still work as usual
Wayland pointers are actually surfaces that we dump image data into periodically to render them as evas images
some small amounts of hack is necessary to make this work, namely blocking X pointers when a Wayland one is in use if we're running a multi-protocol compositor
adds a probably-working wayland framebuffer output module
Additional authors:
Chris Michael <cp.michael@samsung.com>
Signed-off-by: Chris Michael <cp.michael@samsung.com>
Chris Michael
Mike Blumenkrantz