Invoked actions in the order Problem

hechengrong wrote:

> I have a problem with OPS. The problem is that "This action causes
> its child actions to be invoked in the order that they aren't
> specified in the document". XForms 1.0(Second Edition) is descripted
> like that:
>
>         _10.1.1 The action Element_
>
> _This action causes its child actions to be invoked in the order
> that they are specified in the document._
>
> Should OPS implement Action Element like XForms1.0(Second Edition) ?
> If not, How can I invoked actions in the order that they are
> specified in the document?

Yes, Orbeon Forms should implement action as specified in XForms
1.0. And in fact it usually does, with some exceptions, like when you
use xxforms:script, xforms:message, xxforms:show, in other words
actions that require sending back information to the client.

What's the exact issue you are seeing?

-Erik

-- 
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/

hechengrong wrote:

> I have a problem with OPS. The problem is that "This action causes
> its child actions to be invoked in the order that they aren't
> specified in the document". XForms 1.0(Second Edition) is descripted
> like that:
>
>         _10.1.1 The action Element_
>
> _This action causes its child actions to be invoked in the order
> that they are specified in the document._
>
> Should OPS implement Action Element like XForms1.0(Second Edition) ?
> If not, How can I invoked actions in the order that they are
> specified in the document?

Yes, Orbeon Forms should implement action as specified in XForms
1.0. And in fact it usually does, with some exceptions, like when you
use xxforms:script, xforms:message, xxforms:show, in other words
actions that require sending back information to the client.

What's the exact issue you are seeing?

-Erik

-- 
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/

On 12/25/06, hechengrong <[hidden email]> wrote:
>    Thank you for your response. Test case is that:
> Frist Action: submit a xforms instance A and then replace another xforms
> instance B;
> Second Action: do different action with xforms instance B.

Keep in mind that the xxforms:script actions will be executed after
all the other actions. But in the code below they appear at the end of
the action sequence anyway, so that should not make a different,
right?

>            <xforms:action ev:event="DOMActivate">
>                 <xforms:send submission="service"/>
>                 <xforms:action
> if="instance('return')/return-value = 'true'">
>                      <xxforms:script>
>                           alert("if return-value='true', then...");
>                      </xxforms:script>
>                 </xforms:action>
>
>                 <xforms:action
> if="instance('return')/return-value = 'false'">
>
>                      <xxforms:script>
>                           alert("if return-value='false', then...");
>                      </xxforms:script>
>                 </xforms:action>            </xforms:action>

Do you have something particular in mind that you are trying to do and
that doesn't work for you right now?

Alex
-- 
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/

On 12/26/06, hechengrong <[hidden email]> wrote:
>    I want to do that:
> 1. open a modal dialog to show some message, then return 'true' or 'false';
> 2. it will not do any thing when return value of dialog is 'false'; it will
> jump another page when return value of dialog is 'true'.

Here is how I would do this:

1. Put the question you want to ask in an <xxforms:dialog>.
2. When you want to ask the question show the dialog with <xxforms:show/>.
3. In the dialog:
3.1. When the user answers the question with "true" (assuming for
instance that you have two buttons Yes/No), run the <xforms:send> or
<xforms:load> to go to another page.
3.2. When the user answers with "false", close the dialog with the
<xxforms:hide> action.

Alex
-- 
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/