1. The gd patch, can I stick in it? (Yes the windows static hack is evil, but even cygwin uses it so it appears to be a standard "windows is stupid" workaround)
That's fine with me. I haven't had a chance to test though.
2. I still have to fix the shared/static issue for extensions so nix users can build them properly (this week...just a matter of test and commit)
Okay.
3. Are we going to have custom cell renderers? That's the only thing I think we're missing of "cool stuff that other wrappers have"
Not in 2.0 release (see my other email).
4. Cairo - I've discovered a really nice cairo extension, all OO although all the features aren't implemented yet. Thoughts for using this with php-gtk so the 2.10 print stuff can actually be used? (The wrapper currently in PECL isn't that useful and the promised Pierre extension is still vaporware) Or are we pushing this back for the 2.1 release :) code at
shlomil.blogspot.com/2006/10/my-php-cairo-extension.html (which made this message fail last time as "spammy" - wtf?)
How would you integrate it with PHP-GTK? Similar to GD?
5. Can we find some time before the release for a code coverage marathon? (I have a few sitting around here I need to stop being lazy about for that matter)
Sure, but let's not take 100% as the release goal.
Otherwise, yes a final release would be cool. The only other thing (which many not be desired) is to allow php-gtk to build a base extension with the gobject/other glib stuff and allow the gtk portion as an extension (a la pygtk's split into pygtk and pygobject) - but that's just a thought.
Nah, we don't need that. People are not going to use GObject stuff without Gtk.
-Andrei
http://10fathoms.org/vu - daily photoblog