From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O6Qei-0002ok-4I for qemu-devel@nongnu.org; Mon, 26 Apr 2010 11:55:32 -0400 Received: from [140.186.70.92] (port=40355 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O6Qeh-0002oE-0b for qemu-devel@nongnu.org; Mon, 26 Apr 2010 11:55:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O6Qef-0008Hc-Bp for qemu-devel@nongnu.org; Mon, 26 Apr 2010 11:55:30 -0400 Received: from mail-pz0-f204.google.com ([209.85.222.204]:56644) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O6Qee-0008HM-Kv for qemu-devel@nongnu.org; Mon, 26 Apr 2010 11:55:29 -0400 Received: by pzk42 with SMTP id 42so8001336pzk.4 for ; Mon, 26 Apr 2010 08:55:27 -0700 (PDT) Message-ID: <4BD5B761.2060907@codemonkey.ws> Date: Mon, 26 Apr 2010 10:55:13 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [libvirt] [Qemu-devel] Re: Libvirt debug API References: <4BD09A3B.3090001@codemonkey.ws> <4BD1971B.7060907@redhat.com> <4BD1A543.1050004@codemonkey.ws> <4BD1ADA2.2050605@redhat.com> <20100423143656.GG17700@redhat.com> <20100426125424.GC16976@shareable.org> <4BD5A26A.90003@redhat.com> <4BD5A46E.9090808@redhat.com> <20100426145450.GB12919@redhat.com> <4BD5AC71.4080308@codemonkey.ws> <20100426152039.GC12919@redhat.com> In-Reply-To: <20100426152039.GC12919@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: Libvirt , Jiri Denemark , Chris Lalancette , Avi Kivity , qemu-devel@nongnu.org On 04/26/2010 10:20 AM, Daniel P. Berrange wrote: > > For the sake of my analogy, I'd still group cairo in with gtk, not x11. It > is really just a re-implmentation of the GDK drawing layer from GTK. It > still provides a portable higher level abstraction over underlying graphics > & rendering systems it supports. eg, again an app might do the majority of > its drawing with Cairo, but occasionally need to jump outside to use XRender > or OpenGL directly for pieces that aren't supported currently in the cairo > API. > Yeah, that's a fair point. Regards, Anthony Liguori > Regards, > Daniel >