@sams and @AD7six Yes, one element for each input. Performance is not issue here. Finally, you can cache those elements as any other View::element() calls.
This is not only about applying Twitter Bootstrap. FormHelper is not flexible enough and extending large methods is not best solution. It's hard for frontend coders to use Cake forms.. They wont HTML back. I think FormHelper is reaching his maximum now. Code is complicated, a lot of code inside goes to formatting and can be wiped out if templates are used. Only drawback for using templates is case when you need just-a-bit different input in some place. Now you can pass option to helper, but with templates you have two options: - to create new template - to mess up templates using conditional logic inside. I luv this template idea, and I hope templates could fit into existing FormHelper as alternative (option to use templates), without breaking BC and preserving API, but requires a lot of refactoring. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
