El Sat, 07-08-2010 a las 12:14 -0400, Bernie Innocenti escribió:
El Sat, 07-08-2010 a las 11:25 +0200, Tomeu Vizoso escribió:
I'd expect well-written code to call cairo_surface_create_similar()
whenever possible, but there might be hot-spots in our software stack
that assume 32bpp.
On Sat, Aug 7, 2010 at 02:20, Bernie Innocenti ber...@codewiz.org wrote:
El Tue, 03-08-2010 a las 16:26 +0200, Tomeu Vizoso escribió:
This means that graphic operations would be considerably faster on the
XO-1 because to date we are rendering to 24bit surfaces that the X
server has to convert
El Sat, 07-08-2010 a las 11:25 +0200, Tomeu Vizoso escribió:
I'd expect well-written code to call cairo_surface_create_similar()
whenever possible, but there might be hot-spots in our software stack
that assume 32bpp.
Have given a look to gtk+ and the xlib backend of cairo and seems to
On Sat, Aug 7, 2010 at 18:14, Bernie Innocenti ber...@codewiz.org wrote:
El Sat, 07-08-2010 a las 11:25 +0200, Tomeu Vizoso escribió:
I'd expect well-written code to call cairo_surface_create_similar()
whenever possible, but there might be hot-spots in our software stack
that assume 32bpp.
El Sat, 07-08-2010 a las 18:19 +0200, Tomeu Vizoso escribió:
Sounds good, if that gives problems we can consider backporting just that
patch.
If the small patch below is really what was needed, I'm going to feel
quite stupid:
On Tue, Aug 3, 2010 at 7:26 AM, Tomeu Vizoso
tomeu.viz...@collabora.co.uk wrote:
This means that graphic operations would be considerably faster on the
XO-1 because to date we are rendering to 24bit surfaces that the X
server has to convert to 16bit every time.
This Cairo change is in 1.9.8
El Tue, 03-08-2010 a las 16:26 +0200, Tomeu Vizoso escribió:
This means that graphic operations would be considerably faster on the
XO-1 because to date we are rendering to 24bit surfaces that the X
server has to convert to 16bit every time.
Fantastic news!
In order to benefit in Sugar, do
