Re: Gnome/GtkCanvas (was Re: gtk_args_collect & gnome--)
- From: Miguel de Icaza <miguel nuclecu unam mx>
- To: Bertrand Guiheneuf inria fr
- CC: gtk-list redhat com, gnome-list gnome org
- Subject: Re: Gnome/GtkCanvas (was Re: gtk_args_collect & gnome--)
- Date: Tue, 8 Sep 1998 16:50:27 -0500
> What may be Miguel/Frederico decision, it should be quick, because,
> the canvas is gonna be widely used in the next week (it's a fantastic widget)
> by numerous programmers.
Well, if it is going to be wildely used no matter where it is,
then I say we keep it in the Gnome libraries. That way, more people
can start using the utility and sugar functions provided by the gnome
libraries and give their applications a touch of more consistency and
user configurability.
I have also been thinking for another reason to keep the Gnome
Canvas in the Gnome libraries: moving the Gnome Canvas to Gtk will
start by crippling it (image support will get dropped as it requires
Imlib). Then, as the font situation in X sucks so much, we are going
to do something about that in the context of Gnome (where we can
dictate more policy than with Gtk) and specifically, in the context of
the Gnome Canvas (I want to have type1/freetype support as well as
postscript generation).
The Gnome Canvas has the potential of fixing a lot of problems for
the GNOME community and moving it to Gtk will just constrain what we
can do with it, and I dislike this idea very much.
I do not want to be forced to use a minimal subset of features,
just because Gtk has to cause as little grief as possible to their
users or because they dont want to require more libraries to compile
Gtk. So, I think we will keep the Canvas in the Gnome libraries and
the world will be a better place.
Miguel.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]