Re: Re: Announcing PHP-GTK-EDGE

On Jan 30, 2007, at 10:08 AM, Anant Narayanan wrote:

I understand that we're all supposed to be working on API completion at this time; but I can very frankly say that I'm doing the best I can. Sometimes you need motivation to work; and writing an override for a deprecated widget like GtkList (which probably isn't going to be used anyway) isn't as exciting as wrapping GtkSpell. "Work on API completion or else don't work at all" is a pretty hard-line approach IMHO. Let the extensions be in CVS; it couldn't hurt anyone.

Anant, that was never my attitude. API completion is important, but you're free to wrap up other widgets as well. As for the GtkList and other deprecated widgets, they should be at the bottom of the list, as far as API completeness is concerned. If you take a look at gen_gtk.log and gen_gdk.log there are plenty of other interesting functions to override..

I'll withdraw php-gtk-edge as soon as I have the go-ahead for syncing php-gtk-cvs with edge. The following patches are in it: * Support for Gtk+ 2.8 and 2.10

I'd like to finish discussing it first.

* Corrected version of GtkPlug override

That's fine with me, although the patch I saw had some issues.

* The GtkSpell and GtkExtras extensions

These are fine with me.

Oh, and there's nothing "illegal" about php-gtk-edge; and I'm not aware of what's illegal about gnope either. Care to share what's that about?

There's nothing illegal about php-gtk-edge, but I think a duplicate of the source tree is problematic for a variety of reasons. -Andrei