summaryrefslogtreecommitdiff
path: root/canvas
diff options
context:
space:
mode:
authorRadek Doulik <rodo@novell.com>2013-07-08 18:56:33 +0200
committerJan Holesovsky <kendy@suse.cz>2013-07-08 18:57:44 +0200
commit4a9a2c0ed10608d1afcaebaf8bd25059b7a3f4be (patch)
treed56c691e6cbb003ff701b29d06ec71c476abfb3b /canvas
parent3a54294e45f20e7705d06b9aa036a2ba12f56a50 (diff)
Turn Radek's notes into README files.
Change-Id: I904142622ac37b394ddedf62bb7d9c099fc9cab4
Diffstat (limited to 'canvas')
-rw-r--r--canvas/README20
1 files changed, 20 insertions, 0 deletions
diff --git a/canvas/README b/canvas/README
index 0110f5adfd55..2fb141c48148 100644
--- a/canvas/README
+++ b/canvas/README
@@ -24,3 +24,23 @@ 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).
+
+== Cairo canvas ==
+
+cairo canvas is one of backends of canvas component. canvas is mostly
+used for slideshow rendering and also for emf+ rendering. we hoped it
+will even be used by drawing layer, but it didn't happen (yet?) for
+API look at offapi/com/sun/star/rendering/, the implementation is in
+canvas and cppcanvas modules.
+
+cairo canvas backend uses cairo library for rendering. main advantage
+is support of alpha transparency and in some cases accelerated
+rendering.
+
+the backend itself is quite old and stable, not many changes in that
+area lately, mostly changes for emf+ rendering, communication with
+vcl and bugfixes
+
+FUTURE work: look at cairo canvas and situation when it is used
+(mostly slideshow). TODO there still might be more cases when we
+can save some roundtrips when exchanging data with vcl.