I'm trying to allow view authors to be able to use custom UI widgets that
reference the data model, but do not specifically rely on XForms elements.
For example, I'd like the view author to be able to write something like
...
<widget:MatrixVeiw>
<widget:X-Axis ref="Date"/>
<widget:Y-Axis ref="Project"/>
<widget:Value ref="Hours"/>
</widget:MatrixView>
...
where the @ref's point to node-sets (or elements) in the XForms data model.
...
<Timesheet>
<Date>2003-07-29</Date>
<Project>Integration</Project>
<Hours>8</Hours>
</Timesheet>
<Timesheet>
<Date>2003-07-30</Date>
<Project>Integration</Project>
<Hours>6</Hours>
</Timesheet>
...
I had envisioned the xforms-output-prologue transforming elements in the
widget namespace into something that the XForms processor could counsume,
for example
...
<d:table>
<d:tr>
<d:th><xforms:label ref="Project[1]"/></d:th>
<d:td>
<xforms:input ref="Hours[1]"/>
</d:td>
...
In other words, building a table of XForms inputs.
The prologue seems to be the best way to handle the processing of the widget
namespace prior to the XForms output processor. On page 48 of the latest OXF
documentation pdf (Processors Reference), there is a mention of the
xforms-output-prologue attribute on the view element in a controller file. I
specified an xpl file that performs some simple functionality similar to the
logic in the epilogue file. However, nothing in the prologue ever seems to
be executed. I even tried loading a malformed prologue.xpl document and no
error was generated. Any guidance would be much appreciated.
Thanks,
Justin Makeig
--
Center for Document Engineering
University of California, Berkeley
_______________________________________________
oxf-users mailing list
[EMAIL PROTECTED]
http://mail.orbeon.com/mailman/listinfo/oxf-users
