On Nov 4, 2:47 am, Miles J mileswjohn...@gmail.com wrote:
Ive always wanted this. Cakes defaults are pretty handy but once you
want to break out of the norm it gets tedious.
I would also change the HTML structure but thats just me :P
@Sherlock - There's not much overhead in doing a basic
@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.
On Nov 4, 11:41 am, majna majna...@gmail.com wrote:
@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.
Try what you're suggesting and benchmark it before dismissing
performance -
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
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
Those templates could be theme specific (like Twitter Bootstrap) and
IMHO only not-so-easy solvable problem with Twitter Bootstrap and cake
forms is - label wrapped around checkboxes, for both single-ones and
'multiple' (wrapped in unordered lists). Rest of it is easy, thanks to
'className' key
Ive always wanted this. Cakes defaults are pretty handy but once you
want to break out of the norm it gets tedious.
I would also change the HTML structure but thats just me :P
@Sherlock - There's not much overhead in doing a basic PHP include.
On Nov 3, 6:21 pm, 100rk lubomir.st...@gmail.com
In 2.0 you solve this tedious by building/subclassing formhelper.
Using the alias feature and writing your own functions to support your
needed/different template and format.
On Nov 3, 7:47 pm, Miles J mileswjohn...@gmail.com wrote:
Ive always wanted this. Cakes defaults are pretty handy but
