Re: Re: New component for QF: selectfilter

From: Date: Thu, 11 Nov 2004 18:06:12 +0000
Subject: Re: Re: New component for QF: selectfilter
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-34331@lists.php.net to get a copy of this message
Hi On Thu, 2004-11-11 at 17:52, Bertrand Mansion wrote: > Nicolas Hoizey wrote: > > >> Very nice script. > > > >Thanks everyone for the feedback. > > > >Should I now make an official proposal? > > You raise a good question. It looks like your QF element could be useful to > some. There have also been some other element proposals in the past which never > made it into the main QF package because they were incomplete or very specific. > > Personally, I am not against integrating your element into the main package but > everytime we add a new element, it brings new maintenance work for the main > maintainers. The best example was the rewrite of the hierselect element to > support multiple depth levels which took more time than it was supposed to. > > A solution could be to make any new QF element proposals a new QF *subpackage* > with its *own* maintainers. > > This is for us a very important issue because we are currently in the process of > writing HTML_QuickForm4 for PHP5. This will be a major rewrite, with nicer OO > implementation and a LOT less bloat. We hope to make QF4 faster and more > intuitive for the users. > > Having the possibility to use the subpackage infrastructure to handle new > elements proposals would be nice. > > If the infrastructure is already there, then your proposal could become the > first QF element subpackage. IIRC, QuickForm Controller is already a subpackage > of QF, so this shouldn't be too much of a problem. > > In the future, when QF4 will be released, we would of course appreciate that you > adapt your element to the new API, maybe you could then release a > HTML_QuickForm_SelectFilter2 package... > I was actually thinking about this very thing today, i.e. the subpackage stuff for QF, IMHO it would be good (at least for QF4) to split some (or even most?) of the elements from the package, at least hierselect, autocomplete and such specific things that are less commonly used and maybe even could benefit from having it's own release cycle :-) Though only a idea, but might be worth it? Regards Helgi

« previous php.pear.dev (#34331) next »