Slow or fast is obviously application dependent. The original poster didn't complain about speed... The most important thing is never to send to the rendering pipeline data that will not be shown. E.g. in a GIS system if you are zoomed out you don't want to draw small features. And you don't want to send features to be rendered that you know will be clipped. So you may want to use some kind of quadtree to save the relevant features at each zoom level.
That said, I also found cairo too slow for my liking in my image and vector viewer giv, and found that agg was faster.See my tutorial at: http://giv.sourceforge.net/gtk-image-viewer/gtkimageviewer_tutorial.html for an example of how to use agg with gtk. Regards, Dov 2009/4/13 Jose Hevia <jose.francisco.he...@gmail.com> > 2009/4/13 Dov Grobgeld <dov.grobg...@gmail.com>: > > gdk_draw_line() is deprecated. Use cairo instead. > > And the problem with cairo is that is going to be far slower than gdk, > although it provides better output, and could be hardware accelerated. > > http://cairographics.org/FAQ/ > Read "Clipping should only make things faster, right?" > > That's my main problem with cairo. I use my own raster because cairo > is sloooow, and only want to update the region I change. > _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
