On Thu, 17 Apr 2008 13:15:42 -0400, Behdad Esfahbod wrote:
On Thu, 2008-04-17 at 18:07 +0100, Gustavo J. A. M. Carneiro wrote:
+1 too. Though opening the actual generated PDF in evince is always
going to be a more reliable preview than rendering to a widget. There
always will be bugs
On Tue, 11 Dec 2007 21:22:32 +0100, Jürg Billeter wrote:
On Tue, 2007-12-11 at 13:08 -0600, Shaun McCance wrote:
The problem I see with the proposed scheme is that we can't
fit step (e) into it, since 2.12.2 is never in SVN. With our
current scheme, you can do this:
...
The cairo
On Thu, 06 Dec 2007 09:44:55 +0100, Denis Oliver Kropp wrote:
Carl Worth wrote:
For interleaving cairo and non-cairo rendering, cairo provides the
cairo_surface_flush and cairo_surface_mark_dirty APIs. Does
cairo-directfb implement those and does your application use them.
Thanks
On Thu, 06 Dec 2007 21:52:08 +0100, Denis Oliver Kropp wrote:
I'd also like to see that revived:
* @CAIRO_FORMAT_RGB16_565: This format value is deprecated. It has
* never been properly implemented in cairo and should not be used
* by applications. (since 1.2)
Embedded devices
On Wed, 05 Dec 2007 11:09:33 +0100, Denis Oliver Kropp wrote:
CAIRO-DIRECTFB: Use DirectFB for show_glyphs() even if it is unaccelerated.
The software fallback in DirectFB is well optimized.
Hi Denis,
I'm inclined to let anyone who wants to maintain
cairo-directfb-surface.c do whatever they
On Wed, 5 Dec 2007 10:22:08 -0800, Mike Emmel wrote:
Hi Carl Claudio one of the main directfb developers has a lot of cairo
patches setting on the directfb git server.
One can you give him check-in rights for Cairo.
Here's the process to ask for that (ignore the CVS in the title, of
course):
On Fri, 16 Nov 2007 14:04:45 +0100, =?ISO-8859-1?Q?BJ=F6rn_Lindqvist?= wrote:
surface = cairoio.load('foobar.png')
if surface.get_format() in (cairo.FORMAT_ARGB32,):
is equivalent with:
pixbuf = gdk.pixbuf_new_from_file('foobar.png')
if pixbuf.get_has_alpha():
Actually,
On Sat, 13 Oct 2007 00:51:44 +, =?ISO-8859-1?Q?BJ=F6rn_Lindqvist?= wrote:
I have played around with Cairo some more and it seems to me that it
is not fully ready yet. :( Cairo blits and scales much slower than
gdk-pixbuf (software that is)
Do you have some simple test cases to demonstrate
On Fri, 08 Jun 2007 21:15:34 +, rahed wrote:
checking cairo-pdf.h usability... no
checking cairo-pdf.h presence... no
checking for cairo-pdf.h... no
configure: error:
*** Can't find cairo-pdf.h. You must build Cairo with the pdf
*** backend enabled.
You should be able to look at
On Fri, 04 May 2007 10:27:34 -0400, Havoc Pennington wrote:
It's a run-time env variable. I think we don't advertise it at all, it's
more of a defense against people who have strong views on the topic and
prefer undefined behavior probably a crash to just exit ...
And one thing to note here is
On Thu, 3 May 2007 11:11:39 +0200, Benjamin Otte wrote:
I much prefer the cairo model, where basically the
object keeps its own GError and has a function like cairo_status [3]
that gives you the last error that occured.
It's worth pointing out an additional aspect of the
On Thu, 03 May 2007 14:11:02 -0400, Havoc Pennington wrote:
Yeah, I think this keeps the Cairo model from being fully general - it
only works for some types of operations or objects.
Sure. If you want the object to remain usable after an error, then it
shouldn't shut down. And note that that
On Thu, 03 May 2007 15:41:43 -0400, Havoc Pennington wrote:
I'd be for that in the case that the API has a required ending call,
the equivalent of close(). Then you can force error checking on that
last call with a GError or warn_if_unused approach and in theory people
could skip the
On Tue, 24 Apr 2007 00:19:08 +0100, Damon Chaplin wrote:
On Mon, 2007-04-23 at 20:09 +0100, Emmanuele Bassi wrote:
floats. in Clutter, for instance, most of the operations are done using
fixed point algebra and transforming doubles in the public API into
16.16 or 21.11 fixed point numbers
On Mon, 26 Mar 2007 19:19:22 -0600, Hans Petter Jansson wrote:
Also, the last time I checked, valgrind would only let you suppress
messages about invalid accesses, not leaked memory.
No, it definitely allows suppressions for leaked memory, via a
Memcheck:Leak suppression entry. I've included an
On Tue, 27 Mar 2007 17:50:08 +0200, Nicolas Setton wrote:
Interesting, the dashed stroke is exactly what's causing problems -
thanks for the pointer!
Ah, ...
though I *think* it has been adressed since. But if you are running
1.4, that would hint that it still is a problem.
There have
On Tue, 31 Oct 2006 10:26:41 -0800, Carl Worth wrote:
On Tue, 31 Oct 2006 15:26:35 +0100 (CET), Tim Janik wrote:
i.e. using averaging, your numbers include uninteresting outliers
that can result from scheduling artefacts (like measuring a whole second
for copying a single pixel
On Mon, 17 Jul 2006 13:58:41 -0700, Jesse Donaldson wrote:
We're still using v2.6, so folks may not care,
but I'm happy to share our results (once we've obtained them). Also, if
he'd like, I can try to put Mathias in touch with whoever will be
looking at this on our
On Wed, 05 Jul 2006 17:13:20 -0300, Carlos Eduardo Rodrigues Diógenes wrote:
There is any plan about wrapping composite or render in gtk?
The X Render library provides a very low-level way of drawing things
in X. A higher-level library that builds on Render, (or other
systems), and actually
On Tue, 28 Feb 2006 14:07:12 -0800, Bill Spitzak wrote:
4. All attempts to modify the one pixel do the callback function, giving
it the source color, the mask, and the op used, and possibly other
information.
If we were going to do that, then we might as well specify the drawing
operation
On Wed, 01 Mar 2006 11:27:38 +0100, David Trallero Mena wrote:
render everything again there. This new surface I use I refer to as
select surface (hit-surface for you). The color used when re-rendering
is indeed and ID (I have to talk with cairo guys about this) of the
figure (rectangle,
On Fri, 14 Jan 2005 16:39:16 +, J. Ali Harlow wrote:
Ah. I had understood that you were pushing for GDI+ because it gives us
anti-aliased paths and alpha-composited primitives. If GDI will do
what we need then the hardware acceleration, ease of use and
familiarity would all seem to
22 matches
Mail list logo
