So you'd get increased flexiblity (in markup control) but at what cost. additional overhead (an element for each form input) and having to make a range of elements for various differing situations
or maybe I am missing the point - I am certain that you can do this without the need to call a Cake Element for every form element. am I missing something - S On 3 November 2011 22:17, majna <[email protected]> wrote: > Instead of using array based options for FormHelper inputs like: label, > before, after, div, format etc. > maybe HTML templates would be more friendly and easier to customize. For > each input type there will be one Cake element as template. > > Here is an example, a proof of concept on how it may look like: > https://gist.github.com/1337871 > > I think this is more flexible and it does not require for developers > (designers) to master FormHelper API just to customize HTML. > Those templates could be "theme" specific (like Twitter Bootstrap) and > shared as plugin. > There are some drawbacks of course. > > Would you use smth like this? > Comments are welcome > > -- > 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 > -- 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
