Question for the community on Cairo/Directfb integration. Cairo is a 2D drawing package now integrated into GTK. Right now to support it I've basically integrated the offscreen or memory drawing pipeline to use the directfb surface. This works fine for cairo. The problem arises when you wan't to use the directfb surface rendering directly. Since cairo is stateful I'm running into a lot of issues where the direct rendering routines are munging the surface state and messing up the cario state.
My planned fix is to extend the cairo backend to also know how to do all the directfb operation plus act as a surface for cairo rendering. This will allow me to ensure that the state is only modified in one place and provide the basis for replacing some of the backend drawing code of cairo with accelerated directfb ops. The operations will all be avialable just the surface will be hidden in the cairo state object. Can anyone see problems with this approach ? _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
