Re: GObject extension propose (GContainer)

[Fontana Nicola <ntd users sourceforge net>]

> On Thu, 15 Jun 2006, Fontana Nicola wrote:
> > Hi all,
> >
> > I'm a GObject based libraries (for UI purpose and not) user and I often
> > need a generic container to derive my own types. In my opinion, I think
> > this generic container must be included inside the GObject library ... it
> > could be used by a lot of derived libraries providing a common approach.
> >
> > I published my solution - that is, what I am currently using - on
> > sourceforge.
> >
> > http://sourceforge.net/projects/gcontainer/
> >
> > Is it a good idea? Is something planned in this direction? Am I totally
> > wrong?
> >
> > I need feedbacks ...
>
> hi. your gcontainer-1.0.0 looks like an interesting approach to me, but
> i'm not sure it's generally good to put that into stock libgobject.
> the main reason is that container needs are probably pretty variable
> out there (i've come across at least 4 different gobject container
> implementations in free software projects i'm woorking on) and that
> both, making too little assumptions in the child/container interface
> isn't going to be very helpful, albeit making too many has the
> same problem.

Some time ago I've started a communication library based on libgobject and I 
feeled the need of two things: a base object with floating reference and a 
container. After some time, I started an experimental cairo canvas and I had 
the same needs. In both cases, no gtk dependency was requested.

Briefly, I'm not talking about a container that cover all needs and tastes but 
instead about "moving the GtkContainer logic and complexity" from gtk to 
gobject, something similar to what was done for GtkObject and its floating 
reference.

I wrote gcontainer with this in mind (the GContainerable interface is 
"compatible" with GtkContainer and GChildable with GtkWidget). Anyway, my 
solution presents some serious problems: I'm misusing the interface to hide 
as much technical details as possible to the implementing objects.

I know it is a huge task but consider this as an idea or a looooong term 
project: I don't think to be the only one with these needs.

>
> i guess we could add a link to your project from the libgobject docs
> (it should probably have a Contrib section), for people possibly looking
> for a GObject container implementation. that way, gcontainer-1.0.0 gets
> a chance of being reused and maybe extended to something generally
> usefull for GObject applications out there.
>
> > Nicola
>
> ---
> ciaoTJ

Of course I'll be glad to have a link in the gobject documentation. Thank you 
for your availability.

Nicola