[cairo] cairo release 1.12.10 now available
Henry (Yu) Song - SISA
hsong at sisa.samsung.com
Thu Jan 17 07:59:07 PST 2013
cairo-gles has quite performance advantage over cairo upstream, I think more than double normal test cases. For simple fill/paint/mask where you have pixel-aligned drawing, there probably not much difference. The text rendering is fast too.
For IOS, it uses EAGL - I have not looked at it. I have a cairo binding to NSOpenGLContext, https://github.com/csyuschmjuh/cairo-nsgl, You can try it out. Few tests I have performed show it is also the fastest - faster than quartz backend, even with QuartzGL enabled. Maybe it is also a good idea to have cairo to use EAGL.
Android - Not clear what you want, you want cairo at Java API level?
From: cairo-bounces+henry.song=samsung.com at cairographics.org [cairo-bounces+henry.song=samsung.com at cairographics.org] on behalf of Bobby Salazar [bobby8934 at gmail.com]
Sent: Thursday, January 17, 2013 5:28 AM
To: Henry (Yu) Song - SISA; cairo at cairographics.org
Subject: Re: [cairo] cairo release 1.12.10 now available
I am particularly interested in giving this a try on OpenGL ES mobile
devices such as iOS and Android, but I have been holding off on
spending the time to try it out until the code is fully upstreamed.
Has anyone ever tried either of these gl code trees on iOS and/or
Android platforms? If so, is there a significant speed difference
between either code tree over normal image surfaces? And does anyone
have any sample code showing how to get started with a cairo gl
surface on iOS and/or Android?
On 1/16/13, Henry (Yu) Song - SISA <hsong at sisa.samsung.com> wrote:
> No, we have not completely upstreamed our code yet. There are still things
> left to do, there are three large differences that we are trying to resolve
> and upstream
> 1. cairo-gles uses a partial compositor initialization, while upstream gl
> uses full init. We have talked to Chris on this and agree on common
> 2. cairo-gles uses GL_LINES drawing mode for stroke width == 1.0, we will
> upstream this too.
> 3. cairo-gles caches some of the GL states, I will submit a patch to resolve
> this for both cairo-gles and cairo upstream.
> There other differences, we will upstream gradually.
> From: cairo-bounces+henry.song=samsung.com at cairographics.org
> [cairo-bounces+henry.song=samsung.com at cairographics.org] on behalf of Bobby
> Salazar [bobby8934 at gmail.com]
> Sent: Wednesday, January 16, 2013 2:59 PM
> To: cairo at cairographics.org
> Subject: Re: [cairo] cairo release 1.12.10 now available
> Over the past couple of years I've heard a bit of talk about two sets
> of cairo OpenGL code. One in the main cairo code base, and another
> Now with the release of 1.12.10 it mentions the "gradual completion of the
> backend for cairo-gl". Does this mean that the code from the link
> above has been fully upstreamed into the main cairo code base?
> If not, what is left and how are the two code trees different?
> cairo mailing list
> cairo at cairographics.org
cairo mailing list
cairo at cairographics.org
More information about the cairo