From c16158772d64cab8a4ed1f165cab57d307998e78 Mon Sep 17 00:00:00 2001 From: Hossein Date: Tue, 23 Mar 2021 14:20:32 +0430 Subject: Using .md extension/Markdown syntax for modules README Renaming all README files for all top level modules to README.md, applying no content change at this stage to be able to track history of the files. These files should be edited to use correct Markdown syntax later. Change-Id: I542fa3f3d32072156f16eaad2211a397cc212665 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/112977 Tested-by: Jenkins Reviewed-by: Christian Lohmaier --- canvas/README | 46 ---------------------------------------------- canvas/README.md | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 46 insertions(+), 46 deletions(-) delete mode 100644 canvas/README create mode 100644 canvas/README.md (limited to 'canvas') diff --git a/canvas/README b/canvas/README deleted file mode 100644 index b68da4c3bf5c..000000000000 --- a/canvas/README +++ /dev/null @@ -1,46 +0,0 @@ -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 -css::rendering, with css::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). - -== 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. diff --git a/canvas/README.md b/canvas/README.md new file mode 100644 index 000000000000..b68da4c3bf5c --- /dev/null +++ b/canvas/README.md @@ -0,0 +1,46 @@ +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 +css::rendering, with css::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). + +== 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. -- cgit v1.2.3