Re: Re: New component for QF: selectfilter

Bertrand Mansion wrote:

Greg Beaver wrote:

This is a great idea. package.xml 2.0 will also make it very easy for Quickform to recommend versions of elements that are guaranteed compatible with quickform, but allow users to install bleeding-edge work as well.

This looks interesting. Any idea when package2.xml will be released to the world ? A tutorial or some documentation on the new format would be helpful as well.

package.xml 2 is an integral part of PEAR 1.4.0, so as soon as it is released, it will be available. Here is my present roadmap: 1) finish regression testing 2) release 1.4.0a1 3) write docs and fix bugs found 4) release any other test releases needed to fix design flaws and update docs/tests 5) go stable For #1, I have completed testing of package.xml 1.0 support and it should work exactly as PEAR 1.3 plus a few added customization options available through the new PEAR_PackageFile_v1 class, and several critical unfixable design flaws in 1.3 are fixed. I am almost done with testing setters/getters for PEAR_PackageFile_v2 (no more using an array to access the raw data for a package, allowing much better extensibility), and then I need to test the validation features, to make sure that all flaws in a package.xml are documented properly ("missing package name" "package dependency must have either channel or static uri" etc.) Then, I need to complete unit tests for PEAR_Registry's new features, PEAR_Config's new and old features, PEAR_Installer, PEAR_DependencyDB, and every PEAR_Command_* object. I've completed regression tests for PEAR_Downloader, PEAR_Downloader_Package, PEAR_Dependency2, PEAR_Validate, and PEAR_Common. Needless to say, this will take a while, possibly all the way until Jan. 1. Once the initial tests are done, however, it will be very rapid from that point on, and make fixing bugs much more secure, as I can check to see if any remote portion of the app fails with a fix. Yes, this is exhausting work :). Greg