1 UNO-based graphics backend, lesser impedance to modern graphics APIs
4 == The Canvas Framework ==
6 The canvas framework is the successor of the system GUI and graphics
7 backend VCL. Basic functionality is available, supplying just as much
8 features as necessary to provide a VCL-equivalent feature set (except
9 proper BiDi/CTL support).
11 The canvas framework consists of the following two modules, canvas and
12 cppcanvas. Additionally, a new generic graphics tooling is used (but
13 not exclusively by the canvas, Armin's drawinglayer module also make
14 use of it), which resides in basegfx.
16 The UNO API used by the canvas is primarily under
17 css::rendering, with css::rendering::XCanvas
18 being the central interface.
20 == The slideshow engine ==
22 The slideshow engine has replaced the former Impress-embedded
23 presentation framework with a fully independent UNO component, and it
24 is based on the canvas. Some features used there are only available
25 from canvas, like double-buffering, and hardware-accelerated
26 alpha-blending (currently not on all platforms).
30 cairo canvas is one of backends of canvas component. canvas is mostly
31 used for slideshow rendering and also for emf+ rendering. we hoped it
32 will even be used by drawing layer, but it didn't happen (yet?) for
33 API look at offapi/com/sun/star/rendering/, the implementation is in
34 canvas and cppcanvas modules.
36 cairo canvas backend uses cairo library for rendering. main advantage
37 is support of alpha transparency and in some cases accelerated
40 the backend itself is quite old and stable, not many changes in that
41 area lately, mostly changes for emf+ rendering, communication with
44 FUTURE work: look at cairo canvas and situation when it is used
45 (mostly slideshow). TODO there still might be more cases when we
46 can save some roundtrips when exchanging data with vcl.