Michael Leibowitz <[EMAIL PROTECTED]> writes: > I'm new to oo.o development. I'm trying to wrap my head around the > gsl/vcl/canvas layers in oo.o 2.0. Looking in src680-m89, I see a > canvas and cppcanvas directory. Can somebody explain why it is laid out > this way? Thanks. > Hi Michael,
the whole "canvas" story is about migrating the applications' content output, away from ancient VCL OutputDevice, towards a modern, component-based graphics layer. The whole thing is still very much in its infancy, though already used to render the new Impress slideshow. Generally, it's a layered approach, with the canvas module providing the UNO API implementation (for the com.sun.star.rendering.* API), and cppcanvas (and a few other places) adding some convenience (others would say 'syntactic sugar') to the somewhat bare-bones API. The idea behind that was to make implementing the API as easy as possible, to encourage porters to write native bindings to their local graphics subsystem. That didn't work out that well thus far, though there is an X11/cairo implementation on the horizon ;-) Please follow up with specific questions, this is just a general overview. -- Thorsten If you're not failing some of the time, you're not trying hard enough. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
