Re: HTML_QuickForm and Smarty Template

Matthias H. Risse wrote in php.pear.general: > i might be wrong, but i personally dont really see > a real usage for variety of smarty renderers. i tried > arraysmart, smartydynamic and smartystatic and in the > end we're just looping over nested arrays / datastructures. Currently there is only one Smarty specific Renderer named ArraySmarty. An example for using this renderer is shown in SmartyStatic_example.php. You can also use the standard Array renderer with Smarty. This is shown in SmartyDynamic_example.php. > i personally build pretty complex templates and never experienced any > problems just using arraysmarty-renderer. is it really > usefull to have two (or three) diff smarty renderers > which just produce different types of arrays? Different arrays for different use cases. The Array Renderer is very useful for prototyping. Setup all your forms, write only one template - thats all. For individual form design you can switch to the ArraySmarty Renderer - form by form > arent there other problems to solve? Please point us to these Problems. Use http://pear.php.net/bugs/report.php?package=HTML_QuickForm ;-) > i dont want to offend any of the authors or so, but just dont understand > the hype and why we need to make things so complex. Which hype? These Array renderers are not complex. > in the > end the approach always end up with lotsa smarty-macro-definitions > inside of the template which probably doesnt make the party of > the dezign guild happy who are just able to work with in a WYSIWYG > editor.. If your designers are just able to work with an WYSIWYG editor, Smarty is maybe not the best solution. BTW: I think about a CallbackSmarty Renderer (working title) which should adress the requirement to have form definition an form layout inside one template file. ThS. -- http://4bconsult.de