Re: [gtk-list] Re: Canvas.

[John Utz <utz serv net>]

umm i think george has a good point here.

i understand the unwillingness to split the code, but cant it be argued
that g*canvas is a pretty darn lumpy object for a primitive?

a rudimentary gtkcanvas in gtk that gets inherited into a feature rich,
high-policy gnomecanvas seems like a very orthagonal idea...IMHO...

On Wed, 9 Sep 1998, George wrote:

> On Tue, Sep 08, 1998 at 04:54:13PM -0500, Miguel de Icaza wrote:
> > > I agree with owen here ... the canvas has nothing "gnome specific"
> > > it's a fairly general use widget and as such it should be in gtk
> > > or belong to gtk "in spirit" .... Gnome widgets usually set policy
> > > ... the canvas doesn't ...
> > 
> > It uses Imlib.  And in the future, it will use one or more font
> > rendering engines.  As I mentioned previously, crippling the gnome
> > canvas just because someone wants to move to Gtk is a bad idea.
> 
> in that case it should be in gnome libs then :) ...
> 
> how about a compromise though .. split gnome canvas into two widgets,
> a simple gtkcanvas .... and then derive a gnomecanvas from that ...
> the gtk canvas would have the rudimentary stuff, the gnome canvas would
> add font and image support and other stuff that is gnommish ...
> 
> that would give gtk only users a basic canvas, and you could still add
> more gnome type stuff on the gnome side
> 
> George
> 
> -- 
> To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
> 
>