Re: Design Considerations... Description versus Types...

[Havoc Pennington <hp redhat com>]

Suboner@aol.com writes:
> This is a sort of touchy situation because its easy to go either
> direction in extreme, either every object that is created is simply
> a description of other objects, or even GtkWidgets themselves can be
> broken down from being a description of data and data
> relationships. The best way to solve this problem

What's the problem? Is there any reason it matters that a widget is
implemented in terms of more widgets?

> is to have and follow a guide line of what a GtkWidget really is and 
> what it is not,

Ah! The essence of widget...

>  it is very easy, extremely easy for the idea of what a GtkWidget is
> to be lost, or to be generalized until GtkWidget can be just about
> anything anyone wants it to be. And even in the reference guide to
> Gtk+ 1.2, there is lacking of a description of what a GtkWidget is.

A widget is any subclass of the GtkWidget base class that properly
implements the abstract portions of the base class interface.

Havoc