Matthew J. Graham wrote:
> I have a page which can have two views (one standard and one > customized) associated with it depending on a selection in a > previous page so I see two ways of implementing this: > > - just have two different page definitions for the two views and actions > to these: > > <page id="first"...> > <action when="selection = 'standard'"> > <result page="standard"/> > </action> > <action when="selection = 'customized'"> > <result page="customized"/> > </action> > </page> > > <page id="standard">... > > <page id="customized"> > > - some sort of dynamic selection (pipeline result): > > <page id="first"...> > <result page="view"> > ... > > <page id="view" view="selection.xpl"> > > In this case, how can the output of the first page (the value of > selection) into the selection.xpl; is it just through the normal > instance document?
When you navigate between pages, you typically pass information through XForms instances, yes.
Here you can really go either way with two pages or with one page where the view is dynamic. There may be some little benefits or drawbacks of one solution over the other, but both solutions are valid.
-Erik
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
orbeon-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/orbeon-user
