Re: QuickForm 3.0 news: renderers
| From: | Alexey Borzov | Date: | Thu, 13 Mar 2003 15:28:33 +0000 |
| Subject: | Re: QuickForm 3.0 news: renderers | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-14249@lists.php.net to get a copy of this message | ||
13 Март 2003 18:20, Alan Knowles написал:
> ouch.. - is that essential - as I can see it's likely that I'm going to
> end up with lots of little cute widgets doing weird things that I want
> to plug in (that are probably not that usefull to anyone else) - like
> [text input] [textinput] [button] - where you press the button - does a
> popup select and fills in the left two.. - I was hoping to impement that
> as a 'private add-on' to quickforms..
>
> = does this mean that you have to hack the renderer to make it work, or
> are the elements going to be able to stay seperate with a minimal
> knowledge of outputing...
If your element is just a fancy group, then it can probably extend 'group' and
use its rendering logic, if it is like 'date' then you can just write your
own toHtml() method and your element will use default rendering logic.
When I said 'special rendering needs' I meant 'really weird ones': consider
the difference between <input type="text" />, <input type="hidden"
/> and
headers in form.
> This does sound like a case where treecc would be usefull - Aspect
> orientated coding it designed to try and sort out this Visitor class
> interdependant mess... - maybe worth a look..
Please provide a link to this treecc stuff. :]