Account Request : phpHtmlLib

Hello, I would like to move my PHP library/project into PEAR. I am the maintainer of phpHtmlLib, which started out just for rendering of HTML, but has grown into a general purpose library set for building interfaces and documents in PHP. It can build and render XML, HTML/XHTML, CSS, SVG, WML. It has a powerfull HTML form building/processing engine, as well as 'widgets' for XML, HTML, SVG, WML. I have plans to add XUL classes and widgets, for building gecko interfaces on the fly. The current home for phphtmllib lives at http://phphtmllib.newsblob.com, and I have the code checked in to CVS on sourceforge. I know that PEAR has the HTML classes, but I believe phpHtmlLib has a lot to offer for PEAR users. According to the FAQ, PEAR can contain "competing" classes/libs, so I thought I'd ask. I posted here in the mailing last back in February, and got a +1, but didn't hear much of anything else. I want to maintain compatibility as much as possible with the current version of phpHtmlLib and the version after its moved/ported into PEAR. The problem I have is where does phphtmllib fit in PEAR. phphtmllit seems to fit under the HTML as well as the XMLproject spaces, but its much more then just that. I would like to propose a new category called UI, which phptmllib would live under. This would be a generic top level category for building interfaces with php. The GTK classes could live under there, as well as any future classes that are used for building interfaces. The base functionality of building the XML and HTML/XHTML tags as well as the XML and HTML documents would be part of a base package for the new UI_phphtmllib. The WML, SVG (and future XUL) tags and widgets would be part of subpackages UI_phphtmllib_wml, etc. The html widgets can either be another package, or individual packages. Such as UI_phphtmllib_datalist, UI_phphtmllib_NavTable, etc. The form processing engine would be its own package as well under UI_phphtmllib_form. Walt