office-gobmx/canvas
2012-07-04 16:08:13 +01:00
..
inc/canvas Remove unused header files 2012-06-27 13:34:35 +02:00
prj
source fix fdo#51547: revert "Some cppcheck cleaning" 2012-07-04 16:08:13 +01:00
workben re-base on ALv2 code. 2012-06-19 18:00:37 +01:00
Library_cairocanvas.mk targetted improvement of UNO API includes / usage 2012-07-02 14:43:34 +01:00
Library_canvasfactory.mk targetted improvement of UNO API includes / usage 2012-07-02 14:43:34 +01:00
Library_canvastools.mk targetted improvement of UNO API includes / usage 2012-07-02 14:43:34 +01:00
Library_directx9canvas.mk targetted improvement of UNO API includes / usage 2012-07-02 14:43:34 +01:00
Library_gdipluscanvas.mk targetted improvement of UNO API includes / usage 2012-07-02 14:43:34 +01:00
Library_nullcanvas.mk targetted improvement of UNO API includes / usage 2012-07-02 14:43:34 +01:00
Library_simplecanvas.mk targetted improvement of UNO API includes / usage 2012-07-02 14:43:34 +01:00
Library_vclcanvas.mk targetted improvement of UNO API includes / usage 2012-07-02 14:43:34 +01:00
Makefile
Module_canvas.mk
Package_inc.mk Remove unused header files 2012-06-27 13:34:35 +02:00
README
StaticLibrary_directxcanvas.mk

UNO-based graphics backend, lesser impedance to modern graphics APIs
than vcl.

== The Canvas Framework ==

The canvas framework is the successor of the system GUI and graphics
backend VCL. Basic functionality is available, supplying just as much
features as necessary to provide a VCL-equivalent feature set (except
proper BiDi/CTL support).

The canvas framework consists of the following two modules, canvas and
cppcanvas. Additionally, a new generic graphics tooling is used (but
not exclusively by the canvas, Armin's drawinglayer module also make
use of it), which resides in basegfx.

The UNO API used by the canvas is primarily under
com::sun::star::rendering, with com::sun::star::rendering::XCanvas
being the central interface.

== The slideshow engine ==

The slideshow engine has replaced the former Impress-embedded
presentation framework with a fully independent UNO component, and it
is based on the canvas. Some features used there are only available
from canvas, like double-buffering, and hardware-accelerated
alpha-blending (currently not on all platforms).