Re: [PHP-GTK-DEV] Rolling 2.0.1

[email protected] (Andrei Zmievski)
Newsgroups php.gtk.dev
Message-ID <[email protected]>
Hey Elizabeth,

I just rolled php-gtk-2.0.1 tarball and put it in distributions/ on php-gtk-web. 
I think we should juts go ahead and release and we can make 2.0.2 include the 
GTKClist->selection stuff. I'd really us to have much more frequent releases.

Can someone please update the front, download, and changelog pages for the new 
release?

The code coverage stuff looks good, thanks for going through all that stuff.

I hope to continue work on virtual methods soon, which will allow for custom 
cell renderers.

-Andrei

Elizabeth M Smith wrote:
> Hi,
> 
> I see Andrei tagged the next php-gtk version and I know I did a LOT of
> overrides and support stuff in CVS.  With PHP 5.2.6 out the door I'd
> like to do a release shortly, but before we do I'd love to get
> GtkCList->selection wrapped for Madeleine - anyone want to take up that
> one simple override? (It's moving a glist to an array but I'm very busy atm)
> 
> Any other opinions on a new release?
> 
> If anyone is interested I've been working through the gtk docs and
> mapping them to PHP support to weed out bad overrides, bad/missing
> ignores, and missing defs (there were quite a few)  I have 2.12, 2.10,
> 2.8, 2.6, 2.4, and 2.2 new symbols done and I'm working on 2.0 and
> deprecated symbols.  Anyone who wants to see the status it's at
> 
> callicore.net/php-gtk/code-coverage-status.html
> 
> Gray items are ignored and red items are missing, and it's only for gtk.
>  Glib, pango, ATK, et al are not done (yet).
> 
> Also if someone has some time, I think the unixprint support (gtk 2.10+,
> the beautiful green color) would work best as a php-gtk2 extension -
> anyone have the time and/or energy to get that set up?
> 
> Thanks,
> Elizabeth Smith
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.