Hey Anant, Andrei -

>  Before we make another release, I think we should make sure there  aren't 
>  any extant bugs. For example, there's still the cloning crash  that Pablo 
>  described. I replied saying that we may not be able to  support cloning 
>  due to complicated structure of internal Gtk+  objects, but I haven't 
>  heard anything back. Are there other bugs we  are aware of?

We used to have test scripts in CVS for bugs as they arose - we don't have 
anything equivalent now, and it makes it a bit harder to keep an eye on 
them. Perhaps we should start doing that again, because I know prior to 
alpha there were a few that were still broken under win32 but worked 
everywhere else.

> > However, before we go about it, we'll have to decide on whether to
> > include the following:
> >
> > 1) 2.8/2.10 Support. Elizabeth has provided patches for this, and the
> > build system will automatically build the latest version found on the
> > system. I've extended this to work on Linux and OSX.
> 
>  I'm fine with this as long as we make it clear in our builds which 
>  version they support. We should also encourage developers to  explicitly 
>  check for the Gtk+ version in their applications.
> 
> > 2) The GtkHTML3 and libsexy extensions.
> 
>  Sure, these can be included (just the bindings, right?).
> 
> > 4) Move to native Scintilla (Tom's Scintilla) instead of GtkScintilla.
> > This one's on me and I'll get around to it soon enough.

Yay!!! I still have a working copy of that somewhere here, but whether it 
was the final version is a different matter. It's good though!

- Steph 

-- 
PHP-GTK Development Mailing List (http://gtk.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php