Posted by Angel K (po_taka) on 2013-01-28T13:32:58.000+0000
Thank you for the example. Display groups can be emulated this way, but
* u must be sure there is no later decorator that will wrap whole form
* decorators can be added only once. If i want to use htmlTag twice, i need to create new class witch extends htmlTag
* i need to set order to every form
Posted by Angel K (po_taka) on 2013-01-30T07:27:56.000+0000
yep, i didn't know that, tnx :)
Posted by Ralph Schindler (ralph) on 2013-04-05T16:07:01.000+0000
This issue has been closed on Jira and moved to GitHub for issue tracking. To continue following the resolution of this issues, please visit: https://github.com/zendframework/zf1/issues/51
Comments
Posted by Frank Brückner (frosch) on 2013-01-25T08:41:03.000+0000
Hi Angel, can you give us a use case for this? Thanks.
Posted by Angel K (po_taka) on 2013-01-25T11:22:22.000+0000
There is form for "Company". Company can have a lot of phones. Every phone is sub-form. All phone forms should be in one displayGroup
Posted by Frank Brückner (frosch) on 2013-01-25T12:08:15.000+0000
Use the {{setElementsBelongTo}} method for all subforms and the {{HtmlTag}} decorator to add a {{fieldset}} element:
Posted by Angel K (po_taka) on 2013-01-28T13:32:58.000+0000
Thank you for the example. Display groups can be emulated this way, but * u must be sure there is no later decorator that will wrap whole form * decorators can be added only once. If i want to use htmlTag twice, i need to create new class witch extends htmlTag * i need to set order to every form
is much clearer than
Not very powerful arguments, but think about it :)
Posted by Frank Brückner (frosch) on 2013-01-28T19:51:48.000+0000
{quote}decorators can be added only once. If i want to use htmlTag twice, i need to create new class witch extends htmlTag{quote} This is wrong!
Posted by Angel K (po_taka) on 2013-01-30T07:27:56.000+0000
yep, i didn't know that, tnx :)
Posted by Ralph Schindler (ralph) on 2013-04-05T16:07:01.000+0000
This issue has been closed on Jira and moved to GitHub for issue tracking. To continue following the resolution of this issues, please visit: https://github.com/zendframework/zf1/issues/51