On 23/02/12 19:25, Fredrik Holmqvist wrote:
Den 23 februari 2012 20:02 skrev Urias McCullough<umccullough@xxxxxxxxx>:The old Cairo BeOS code tried to wrap everything like this - and it was horrible. Cairo is a C API - Firefox created a C++ wrapper for it called Thebes... but that doesn't resolve the issue of having to build a C++ backend surface that integrates into Cairo. I think BeOS is the only platform that did that previously, and it never worked completely right. I suspect that code has since been excised, as it was unmaintained, and out of date.And to add to that, the reason Firefox is ditching Cairo is because it is very inefficient and has a poor API, while Skia seems to be better. I'd go for Skia, I've even been looking at the code from time to time, and it looks like it is an 'easy' port. See what Skia says about porting: http://code.google.com/p/skia/wiki/Roadmap
I've seen that Skia document, it does sound promising. Cairo with the image backend should compile pretty much out of the box too though. I don't think either of them will be a massive problem at that level (famous last words...)
There is some BeOS backend code in the current cairo, but it only implements conversion from BBitmap to cairo's image surfaces. None of the drawing functions are implemented with BeAPI (but as is hopefully clear, I don't think we want to implement them anyway).
/Fredrik Holmqvist, TQH