Re: New HTML Form class for PEAR
| From: | Tomas V.V.Cox | Date: | Sat, 01 Sep 2001 20:39:18 +0000 |
| Subject: | Re: New HTML Form class for PEAR | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-1752@lists.php.net to get a copy of this message | ||
Stig Sæther Bakken wrote:
>
> ["Tomas V.V.Cox" <cox@idecnet.com>]
> > Bertrand Mansion wrote:
> > >
> > > I would like to commit it. Where should I put it ?
> > > Here is its composition :
> > >
> > > Form.php
> > > |
> > > +- Form directory ---
> > > - button.php
> > > - checkbox.php
> > > - date.php
> > > - element.php
> > > - file.php
> > > - group.php
> > > - hidden.php
> > > - image.php
> > > - input.php
> > > - password.php
> > > - radio.php
> > > - reset.php
> > > - select.php
> > > - submit.php
> > > - text.php
> > > - textarea.php
> > >
> > > and it all depends on Html_Common which is also used by Html_Table.
> > > I know it is a bit difficult now with the new directory structure.
> > > People understanding this structure could give me a clue. Thanks.
> > >
> >
> > I think we should "open" a subcategory of HTML called Form, and there
> > put html forms related things. For your class, for example use:
> > HTML/Form/Quick/ and the directory in pear/ module of CVS could be
> > HTML_Form_Quick (you know, -Quick- or whatever you want (what about Form
> > Builder?)).
> >
> > So could get:
> > require 'HTML/Form/Builder.php';
> > $f = new HTML_Form_Builder;
>
> Why not HTML_QForm, HTML_QuickForm or something like that? It's a
> replacement for HTML_Form after all, so it shouldn't look like a
> "sub-package", which IMHO HTML_Form_Quick would.
>
Umm.. didn't know it will be a replacement for Form. If it is so,
HTML_Form would be the right choose, to don't break the convention :-?
Tomas V.V.Cox