bulia byak wrote:
On 1/22/07, Joshua A. Andler <joshua@...533...> wrote:
With this refactoring/integration, it's also a good time for us to really reorganize code and do some janitorial work. It also presents an optimal time to look into what will be necessary for cairofication.
I read complaints about cairo from sK1 people - after switching to cairo display they claim it's not too fast (even with glitz) and breaks down on paths with 1000+ nodes. So perhaps we should not hurry with cairofication.
No one will disagree about Cairo's current speed. If we are doing other refactoring though, it wouldn't hurt for us to look into what needs to be done for an eventual renderer replacement. Do we really want to solely maintain a renderer forever when we can get other improvements for free with a shared library?
I know that the main goal of the current dev cycle of Cairo is performance improvement (last time I checked there was major work going on for tessellation). Additionally, given that our renderer is faster, perhaps our devs could help improve the speed of Cairo (as we're pitching in for PDF improvement).
I'm not advocating a switch anytime soon, I'm just thinking it would smart to develop a plan at the time other things are being refactored. This way if the Cairo guys figure out some super-speed voodoo and we really want to switch, it will be that much easier (and potentially faster).
-Josh