http://www.nabble.com/How-to-make-a-good-use-of-Elements-and-DRY-principe---tf4279200.html#a12213971
Ski-3 wrote:
>
>
>> you can send a variable to the element:
>> renderElement('my_element', array('data' => $data));
>
> Hi,
>
> Thanks, I have been trying that, but the idea was to re-us
I had a related problem: I want to render , say, a table of categories
in the view, and then i want to use an ajax submission to update that
table again. I created the table as an element included in the view,
of course. in order to avoid writing a view for every different
element that i want to
Hi,
> If I understand you right, it sounds like you may wish to go down the
> ajax route.
> In essence, have an action for the parent that renders all the stuff
> it needs to do,
> but has placeholders (div's) that you preload with child actions (ie a
> form).
Thanks for your answer - I had a
On 7/2/07, Ski <[EMAIL PROTECTED]> wrote:
> I am writing an application which enables editing of data for a
> parent model and a data for a list of child models in a single view.
>
> To make the code easier to re-use, I would like to keep the views
> for the parent and child separate - as the
> you can send a variable to the element:
> renderElement('my_element', array('data' => $data));
Hi,
Thanks, I have been trying that, but the idea was to re-use the
views I have already without having to change them.
I "changed" the "standard" edit form over to an element by moving
the fi
you can send a variable to the element:
renderElement('my_element', array('data' => $data));
it's really useful :)
spark
On 7/2/07, Ski <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am writing an application which enables editing of data for a
> parent model and a data for a list of child model
