Re: Re: [php-gtk-cvs] cvs: php-gtk /ext/gtk+gtk.overrides

From: Date: Sat, 21 Jul 2007 02:53:21 +0000
Subject: Re: Re: [php-gtk-cvs] cvs: php-gtk /ext/gtk+gtk.overrides
References: 1 2 3 4 5 6 7  Groups: php.gtk.dev 
Request: Send a blank email to php-gtk-dev+get-3932@lists.php.net to get a copy of this message
Hi both,
I know a simple "grep" or a "rpl" does the work (no need for scripts Elizabeth), but it opens precedents. If we change these constants today, we will be changing method names tomorrow and we'll start having incompatible versions among the same encarnation of php-gtk2... And this makes me really worried. Bob told us there souldn't be books about php-gtk because there is not even an stable release. But since the API was defined and we just needed a major API coverage, there was no reason to delay this. I believe that a techonogy need good developers to become a sucess but need evangelizers also.
Actually, if you look at other language wrappers, you'll see they all have their constants for gtypes in gobject as well - take a look at pygtk and perl's GTK2 and ruby's wrapper - why should PHP be the only ones putting constants from GLib in C into the GTK namespace? By the way, this isn't the first change that has happened, and we have "changed method names" - there were quite a few just between the alpha and the beta. The point is to have an intelligent API that people coming to PHP-GTK2 from other GTK implementations will understand - as well as creating an easy to use tool for those who come from the PHP community. Why are we worrying about BC with alpha and beta versions?
You're both right, and you're also both wrong. Pablo, it's not the start of a revolution, don't panic :) Elizabeth, I agree that having gobject play the role it should is a big deal. At the same time, there are PHP-GTK users (and books) to consider; we've been slow in making changes and releases (more my fault than yours as we're all aware) and the users have come to regard the API as more or less stable through that. So maybe the next time something comes up that's going to rattle the API it'd be a good idea to discuss it on the dev list directly beforehand so that everyone affected can weigh up the pros and cons? We aren't all on irc, and I'm so old now my memory doesn't stretch back to March :) If it's any use to anybody, I don't think there's anything else left that smells that badly wrong in PHP-GTK 2. (Except possibly the level of reflection, but let's not go there.) - Steph
-- PHP-GTK Development Mailing List (http://gtk.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php


« previous php.gtk.dev (#3932) next »