Hi,
During the LSB desktop testing on Fedora we recently (FC5 test3
and final release) found that there is a patch
gtk+-2.8.10-set-invisible-char-to-bullet.patch added by Fedora
developers. This patch is breaking some of our tests and hence the
question.
The patch is changing the default
> These are not ABI breakages with any platform ABI I'm aware of in
common
> use. GTK+ relies on two basically universal properties of C ABIs:
>
> - Functions can be called with more arguments than they are expecting
> - Functions that return a value can be called as if they returned
>no val
Hello,
Here
are the few changes I found between 2.6 and 2.8 version GLIB.
Return types of interfaces g_tree_remove and g_tree_steal
are changed from void to gboolean.
Return type pf gtk_text_attributes_ref interface is changed
from void to GtkTextAttribute *
Similar
>
> It should generally be opaque to the user that gsize is not
> a typedef for size_t, so you could definitely define it that way for
> the LSB. However, you'd need to include a footnote to the effect:
>
> 1) This definition should not be taken to imply that including
> glib.h necessarily i
>
> What we try to do is to to match the type of size_t on the system;
> for 64-bit platforms, that isn't really a problem ... size_t will
> be 'unsigned long', but on 32-bit platforms it could either by
> 'unsigned int' or 'unsigned long'.
>
So, on 32 bit platforms, why not typedef it as 'unsig
Hello,
For IA32 gsize (found in glibconfig.h) is defined as: typedef
unsigned int gsize;
For IA32-64bit extn and IA64 (Itanium) the definition is:
typedef unsigned long gsize;
Is this intentional? The documentation does not mention anything about
this.. It says: unsigned int only
Thanks Matthias. Please see my comments in line below:
> -Original Message-
> From: Matthias Clasen [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 05, 2006 12:47 PM
> To: Banginwar, Rajesh
> Cc: gtk-list@gnome.org; gtk-devel-list@gnome.org
> Subject: Re
Hello,
Looks like my earlier message got lost during the holidays last
month.
Anyway, LSB desktop project is announcing the availability of GTK
(including Glib, ATK, Pango and GTK) specification at:
http://www.linuxbase.org/spec//book/Toolkit_Gtk/Toolkit_Gtk.html.
This specification will
> -Original Message-
> From: Owen Taylor [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 12, 2005 10:21 AM
> To: Tristan Van Berkom
> Cc: Banginwar, Rajesh; gtk-devel-list@gnome.org
> Subject: Re: Usage of GTK+ headers
>
> On Wed, 2005-10-12 at 10:47 -0400,
Hello,
Many of the GTK+ libraries have one or more top
level header files. E.g. Glib has glib.h, gdk-pixbuf has two gdk-data.h and
gdk-pixbuf.h and so on… My question is about what applications typically use?
Do they use just the top level header only? Or is it ok to use the sp
,
-Rajesh
> -Original Message-
> From: Owen Taylor [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 26, 2005 5:50 PM
> To: Banginwar, Rajesh
> Cc: gtk-devel-list@gnome.org; gtk-list@gnome.org
> Subject: Re: Pango questions in LSB context
>
> On Mon, 2005-09-26 a
Hi,
Here some new questions that came up during LSB inclusion
process for all the Pango libraries:
- All of libpangox-1.0 library is deprecated. LSB will not include this.
Is that Ok? Any comments?
- Many of the interfaces in pango* libraries are ifdefed by
PANGO_ENABLE_ENGINE and PANGO_E
> -Original Message-
> From: James Henstridge [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 21, 2005 9:55 PM
> To: Banginwar, Rajesh
> Cc: gtk-devel-list@gnome.org
> Subject: Re: Question around GOnce structure in Glib
>
> Banginwar, Rajesh wrote:
>
> >
Hello,
We are currently in the process of standardizing
GTK+ libraries in LSB-Desktop project. During the process, I ran into the GOnce
structure in Glib library. I will like to understand why the member variables
of this structure are declared volatile. I am trying to find out
I am really glad to see the intention of keeping the ABI same even with
3.0 release.
As we are going to include GTK 2.4 or 2.6 (based on distro feedback;
e.g. Redhat ships with 2.4) in the first release of desktop module of
LSB, having ABI compatibility even after platform consolidation is a
welc
info regarding licensing of the existing
VTS project.
Thanks,
-Rajesh
> -Original Message-
> From: Stefan Kost [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 11, 2005 3:03 PM
> To: Banginwar, Rajesh
> Cc: gtk-devel-list@gnome.org
> Subject: Re: GTK VTS project upd
r that.
I think the GTK community can use it for their regression testing. Hope
we can find another use for the VTS (in addition to LSB).
Thanks,
-Rajesh
> -Original Message-
> From: Luis Villa [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 11, 2005 1:45 PM
> To: Banginwar,
be interested in using it?
Thanks,
-Rajesh
> -Original Message-
> From: Luis Villa [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 11, 2005 12:04 PM
> To: Banginwar, Rajesh
> Cc: gtk-devel-list@gnome.org
> Subject: Re: GTKVTS question
>
> On 8/11/05, B
Hello,
I am resending part of my earlier question here.
I am trying to assess the usefulness of GTKVTS project to GTK community for
regression or other kind of testing. We are using it for LSB runtime testing
when we add GTK library set to LSB.
Also, we will really appreci
here... What kind of tests are you
thinking of creating? Do you have any additional information?
Thanks,
-Rajesh
> -Original Message-
> From: Stefan Kost [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 01, 2005 10:37 AM
> To: Banginwar, Rajesh
> Cc: gtk-devel-list@gnome.or
Hello,
To recap earlier discussion on this topic here, we (LSB WG) have
started looking at GTKVTS project (from GTK CVS) for our runtime
testing. We are currently getting it up to date and will start adding
remaining test cases. Currently the project covers only the libgtk
library partially
21 matches
Mail list logo