Hi all,
I recently found the file canvas/overview.txt that says that in the future VCL is going to go away eventually and canvas + cppcanvas will replace it.
What does this mean to porters like Mac OS X ppl? I know that VCL is not going away for a long time, but is the idea really that canvas will eventually take care of all the necessary graphics work (including creating windows and handling fonts)?
I'm currently investigating the cws:s cairocanvas + cairofixes01. It seems that at least for modules canvas and cppcanvas, the only needed changes to get it building on Mac OS X would be to convert from X -> Mac the files:
canvas/source/cairo/cairo_cairo.cxx
canvas/source/cairo/cairo_helper.cxx
canvas/source/cairo/makefile.mk
canvas/source/tools/image.cxx
All the other code is generic Cairo/OOo stuff. This would be possible, because the CVS versions of cairo and glitz are already working natively with Mac OS X.
(see: http://developer.imendio.com/wiki/Gtk_Mac_OS_X/Build_Instructions for instructions on how to build native cairo. Native glitz seems to be already available from fink.)
In the other modules, cairo is at least used in: svx/source/dialog/optgdlg.cxx and indirectly in the vcl. These may need changes as well.
So, is canvas currently actively used anywhere, when running OOo (
e.g. OOo 2.0.2)?
Is there any advantage now or in the future to port cairo canvas to Mac OS X?
Mox
--
Mox on G
- [porting-dev] Porting work wrt (cairo) canvas? Mox
- Re: [porting-dev] Porting work wrt (cairo) canvas? Thorsten Behrens
