I would suggest to implement something like a tag (i.e.
<call-parent-actions>) that will let to call the parent actions like this:
<form name"formP">
<actions>
<action1>
<action2>
</actions>
</form>
<form name"formC" extends="formP">
<actions>
<actionA>
<call-parent-actions>
<actionB>
</actions>
</form>
In this way the user can have parent form actions executed before or after
the child actions. It will be also possible to have them NOT executed if the
<call-parent-actions> tag is not included.
-Bruno
2008/8/31 Adrian Crum <[EMAIL PROTECTED]>
> That's interesting - the menu widget extends actions, but the form widget
> replaces them.
>
> Having the form widget extend actions would be a simple change to make.
>
> Any objections?
>
> -Adrian
>
>
> --- On Sun, 8/31/08, Bruno Busco <[EMAIL PROTECTED]> wrote:
>
> > From: Bruno Busco <[EMAIL PROTECTED]>
> > Subject: Adding actions instead of replacing them in extended forms
> > To: [email protected]
> > Date: Sunday, August 31, 2008, 2:08 AM
> > Hi,
> > when extending a form is there a way to ADD actions to the
> > ones defined in
> > the original form?
> > What I see now is that actions defined in the original form
> > are completely
> > replaced by the actions defined in the extended form.
> >
> > Thank you,
> > -Bruno
>
>
>
>
