9ac86f484b
* As UCB is only ever initialized with "Local"/"Office", remove this configuration vector completely. The "create" ctor creates an instance internally initialized with those "Local"/"Office" keys. Special (test) code can still instantiate an uninitialized one via plain createInstance. And for backwards compatilibity process startup still ensures to create an initialized instance early, in case there is still code out there (in extensions) that later calls plain createInstance and expects to get the already-initialized (single) instance. * XInitialization is an "implementation detail" of the UniversalContentBroker service, do not expose in XUniversalContentBroker. * ucbhelper/configurationkeys.hxx is no longer needed and is removed. * ucbhelper/contentbroker.hxx is an empty wrapper and is removed; however, that requires ucbhelper::Content constructors to take explicit XComponentContext arguments now. * The only remaining code in ucbhelper/source/client/contentbroker.cxx is Android-only InitUCBHelper. Is that relevant still? Change-Id: I3f7bddd0456bffbcd13590c66d9011915c760f28 |
||
|---|---|---|
| .. | ||
| inc/canvas | ||
| prj | ||
| source | ||
| workben | ||
| Library_cairocanvas.mk | ||
| Library_canvasfactory.mk | ||
| Library_canvastools.mk | ||
| Library_directx9canvas.mk | ||
| Library_gdipluscanvas.mk | ||
| Library_nullcanvas.mk | ||
| Library_simplecanvas.mk | ||
| Library_vclcanvas.mk | ||
| Makefile | ||
| Module_canvas.mk | ||
| Package_inc.mk | ||
| 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).