hi,
yesterday I committed a first batch of cleanups to the GObject docs.
http://developer.gnome.org/doc/API/2.0/gobject/index.html
IMHO this is a crucial documentation for the GNOME platform and it can
be improved further. Marc-Andre Lureau and Zeeshan Ali already joined
in the quest to impro
Great work so far!
A point I miss in the tutorial is to mention the G_DEFINE_TYPE()-like
macros which should be prefered over manually defining a _get_type()
function whenever possible. As I see it this affects the following sections:
Boilerplate code
How To define Interfaces?
How To define imple
On Thu, Feb 08, 2007 at 08:44:50AM +0100, Stefan Kost wrote:
>
> What I like to ask you is to reply to
> this mail and tell us what you don't understand yet, point out parts
> that can be improved, let us know if there are some nagging concerns
> about the way GObject works.
Deriving from c
Hi,
Quoting "David Ne?as (Yeti)" <[EMAIL PROTECTED]>:
> On Thu, Feb 08, 2007 at 08:44:50AM +0100, Stefan Kost wrote:
>>
>> What I like to ask you is to reply to
>> this mail and tell us what you don't understand yet, point out parts
>> that can be improved, let us know if there are some nagging c
Sorry, I forgot a CC to the list.
On 2/9/07, Shixin Zeng <[EMAIL PROTECTED]> wrote:
> Thanks. But I want some explanation about the interface of gobject. I
> can't understand what it is from a sentence like "GType's Interfaces
> are very similar to Java's interfaces." because I know nothing about
Shixin Zeng wrote:
> Thanks. But I want some explanation about the interface of gobject. I
> can't understand what it is from a sentence like "GType's Interfaces
> are very similar to Java's interfaces." because I know nothing about
> Java, and I don't want to dig into Java just for this concept.
>
On Fri, Feb 09, 2007 at 01:42:19PM +0100, Stefan Kost wrote:
> >Deriving from classes that implement interfaces and changing
> >the implementation would worth an explanation and example.
>
> Huh, sounds scary.
> ...
> Do you have pointers to an example?
I must admit while I do this in some real w
On Sat, Feb 10, 2007 at 10:38:11PM +0100, David Nečas (Yeti) wrote:
>
> A testing (non-real world) example is attached
Maybe this time I won't forget?
Yeti
--
Whatever.
===
#include
/***
> A point I miss in the tutorial is to mention the G_DEFINE_TYPE()-like
> macros which should be prefered over manually defining a _get_type()
> function whenever possible.
I never did get that G_DEFINE_TYPE() stuff at all... It'd be good to see some
clear documentation on it.
Fredderic
On Sun, Feb 11, 2007 at 06:26:51AM -0500, Freddie Unpenstein wrote:
>
> > A point I miss in the tutorial is to mention the G_DEFINE_TYPE()-like
> > macros which should be prefered over manually defining a _get_type()
> > function whenever possible.
>
> I never did get that G_DEFINE_TYPE() stuff a
I've read it once more, with the example in David Nečas (Yeti)'s
email. I think I understand the interfaces a bit more.
But I have some other questions:
1) Is interface the GObject's way to implement multiple inheritance?
To my understanding, interface is a method to share some
resources(data, m
Hi,
Shixin Zeng wrote:
> I've read it once more, with the example in David Nečas (Yeti)'s
> email. I think I understand the interfaces a bit more.
>
> But I have some other questions:
>
> 1) Is interface the GObject's way to implement multiple inheritance?
>
> To my understanding, interface is
On Mon, Feb 12, 2007 at 02:05:27PM -0600, Shixin Zeng wrote:
>
> 1) Is interface the GObject's way to implement multiple inheritance?
It's the other way round -- whether for GObject or not.
Interfaces (in the more abstract sense) are the primary
entities. Interfaces tell what an object can do,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 12, 2007 at 09:49:46PM +0100, David Nečas (Yeti) wrote:
> On Mon, Feb 12, 2007 at 02:05:27PM -0600, Shixin Zeng wrote:
[...]
> > 2)How its intefaces handled, when a class is derived? Will the child
> > classes possess the same interfaces,
> > > A point I miss in the tutorial is to mention the
> > > G_DEFINE_TYPE()-like macros which should be prefered over
> > > manually defining a _get_type() function whenever possible.
> > I never did get that G_DEFINE_TYPE() stuff at all... It'd be
> > good to see some clear documentation on it.
Hi,
the G_DEFINE_TYPE stuff is on the list since the very beginning.
In part I (Concepts) we will explain it the long way, but mention
G_DEFINE_TYPE. In part IV (Tutorial) we will use G_DEFINE_TYPE. You
should always use it if it fits.
Stefan
Quoting Freddie Unpenstein <[EMAIL PROTECTED]>:
I'm trying to understand the Signals in GObject and I have lot of
questions not covered by the doc:
1) The text "when they register a closure to be invoked upon the
signal emission" is not clear what is it a "closure" or what is the
diference with a callback
2) if a signature for a callback is:
On Wed, Feb 14, 2007 at 02:52:02PM -0600, Daniel Espinosa wrote:
> 1) The text "when they register a closure to be invoked upon the
> signal emission" is not clear what is it a "closure"...
Not even when reading the tutorial in order and therefore
getting to this just after reading a whole sectio
May be a complete example on how put all together will be usefull
2007/2/14, David Nečas (Yeti) <[EMAIL PROTECTED]>:
> On Wed, Feb 14, 2007 at 02:52:02PM -0600, Daniel Espinosa wrote:
> > 1) The text "when they register a closure to be invoked upon the
> > signal emission" is not clear what i
Thanks for doing this, this is really important and it's been incomplete for
too
long.
Stefan Kost wrote:
> GType's Interfaces are very similar to Java's interfaces. They allow
> to describe a common API that several classes will adhere to.
> Imagine the play, pause and stop buttons on hifi
20 matches
Mail list logo
