How does this affect developers? If you add a new element to QuickForm, that is a container (like 'group') or has some special rendering needs (like 'hidden') then you have to add an abstract renderMyElement() to HTML_QuickForm_Renderer, and implement the logic in all of its subclasses. If you want to add a new renderer, you just have to implement all the methods of HTML_QuickForm_Renderer in it.
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...
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..
Regards
Alan
Well, I'm writing this in hope that it (and the questions that you ask) will serve as a basis of future renderer documentation. :]
--
Can you help out?
Need Consulting Services or Know of a Job?
http://www.akbkhome.com