making pipeline available in theme*.xsl?

I've got the look and feel for a site set up in a config/theme*.xsl
file.  I'd like to have the currently static html navigation menu be the
result of a pipeline in the theme file; maybe have an xsl variable bound
to the output of a pipeline?  What's the syntax for binding that?  Is
there a better way?


--



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Mike,

You can add a custom input to the oxf:xslt processor that calls the
theme, e.g.:

<p:input name="my-navigation" href="#my-navigation"/>

where #my-navigation refers to the output of the XPL that produces your
navigation info.

Then in the XSLT, use doc('input:my-navigation') to refer to the custom
input.

The drawback of course is that you have to modify the epilogue.

-Erik

Mike Leary wrote:
> I've got the look and feel for a site set up in a config/theme*.xsl
> file.  I'd like to have the currently static html navigation menu be the
> result of a pipeline in the theme file; maybe have an xsl variable bound
> to the output of a pipeline?  What's the syntax for binding that?  Is
> there a better way?

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



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws