Re: New home for form stuff

From: Date: Mon, 13 Aug 2001 11:39:35 +0000
Subject: Re: New home for form stuff
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-1432@lists.php.net to get a copy of this message
le 13/08/01 13:04, Ulf Wendel à ulf.wendel@phpdoc.de a écrit : > Stig Sæther Bakken wrote: >> Please put it in /pear/HTML_OOH_Form (or however you want to >> capitalize it). Nothing new should go into php4/pear. > > Yepp, I've choosed a slightly different place in the /pear module and > not the php4/pear module. The path I've used is /pear/HTML/OOH_Form. > HTML_OOH_Form does not fit very well to the idea of a general HTML/ > directory. > As I already said in my commit message: please remember this ooh form > rewrite is highly unstable. API, filenames - just everything may and > will change at any time. Work will be finished in november 2001. Why don't you commit it when it is finished ? ITX is not finished neither and it's been a long time since you said you would do something about it. I have asked you some questions about it and never had replies so I went to the conclusion that you want to do it by yourself. In the meanwhile, people are trying to use it and lose time wondering why it does not work (ex : addBlockFile). With Adam Daniel, we have made an OOH_Form class and are willing to commit it too. How does this fit in PEAR ? Do we need two classes ? Our class is a subclass of HTML_Common, uses HTML_Select and can work with HTML_Table, all are already part of PEAR, are maintained and work well. Will OOH_Forms leave PHPLIB CVS (even on the new sourceforge repository) ? How do you maintain 2 sources in 2 different CVS repositories ? (Same remark for ITX which I modified in PEAR and not in PHPLIB as I don't have CVS access). My opinion is : please commit it when it is usable. Bertrand Mansion Mamasam

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