Tue Aug 20 03:15:27 EDT 2002 $Id: README.xml,v 1.2 2002/08/27 18:56:08 rick Exp $ rick frankel cyberCode consulting inc

rick@rickster.com

xforms.xsl xforms to html template xforms.css Example CSS styles for above output test.xml Test input PostFilter.pm Apply posted data to embedded instance data (see below) README.xml source to this document xsltproc --param list-size 3 xforms.xsl test.xml There are 2 default (xsl:params) in the template. One controls the formatting of lists. The other controls the encoding of the instance data into the hidden form field _instance (see below). Their defaults are: list-size 5 encode-instance-data 0 (false() The stylesheet has been tested with the xsltproc command-line processor. The template requires an xslt processor which supports the following exst extensions: str:tokenize for handling multi-valued select instance data dyn:evaluate for instance data func:function for accessing model nodes and more. Note that the dyn prefix is mapped to the http://icl.com/saxon namespace, which is available in the current release version of libXML. When the cvs version is released, the evaluate function will also be mapped into the http://exslt.org/dynamic namespace and the template can be changed. However, it seems that at least for the moment, the cvs version of libXML is also backwards compatible w/ the saxon namespace. The template attempts to handle as much of the Xforms RFC as possible w/o client side procesing or multi-pass transformations. Obviously, w/o client side processing things such as events, actions, control flow and interleaved model specific controls cannot be handled. This version operates in xslt push mode. Any text or nodes (w/attributes) not in the xforms namespace are copied to the output as is. It handles multiple forms, but assumes that ALL the controls for each form are wrapped in an outermost xforms:group, in the same sense as binding elements are considered outermost in in section 7.3 of the xforms spec (that is, the xpath expression ancestor::xforms:group returns the null set). It also assumes that the input contains all non xforms tags (e.g., html, head, body) required to generate a valid output document. selectMany bindings are handled (I think) per the spec. That is, the instance data is assumed to be a space separated list of data. Currently, nodeset attributes are assumed to be relative to xforms:instance (the root of the pseudo document as defined in the spec), as I cannot deduce from the spec whether they inherit outer context. If you want to bind a itemset to a relative reference, you can use a bind attribute. The bind element will be parsed as a relative path. An xforms::group with the class attribute no-display can be used for context grouping and will not generate a 'div' element in the output. This is useful for generating instance context per section 7.3 of the spec without breaking e.g, a css table model. The template also ignores any caption, hint or common-attributes (class, accessKey) associated with the group. Name attributes on the html form elements are generated according to the spec. That is, if the encoding is application/x-www-urlencoded, the name will be the local-name() of the data node. Any other encoding (default multipart-form-data) will be the xpath to the data. Since this implementation does not allow in-place editing of the instance data on the client, the OO perl library PostFilter.pm has been provided to perform this function on the backend. If value of the stylesheet parameter encode-instance-data is true (1), the instance data for the submitted form will be html-encoded into the hidden form parameter _instance. The PostFilter package provides one method (other than new), parse, which takes a single argument, a hash of the cgi parameters and returns a libXML document containing the updated instance data. A sample cgi script using PostFilter is provided in t/filter_test.cgi. If an instance of XML::libXML is not passed in as the named param parser, it will be instantiated in the new function. The parse function takes a single argument, a reference to hash as returned by CGI::Vars. It returns an XML::LibXML::Document, with an xforms:instance root element. supported template uses prefix xf: elements and attributes in other namespaces copied verbatim mutiple models allowed. controls for each form must be contained in an outer group element. The model used will be either the first model in the document, or the model specified by the first element found via the xpath expression ancestor:xf:*[@model]. extensionFunctions are not supported. Supported for inline content, xlinks not supported not supported supported action supported mediaTypeExtension supported method supported version not-supported indent not-supported encoding supported mediaType not-supported omitXMLDeclaration not-supported standalone not-supported CDATASectionElements not-supported replace not-supported not supported xlink not supported not supported not supported supported supported supported, default not supported not supported schemas not supported not currently used. not currently used supported, class="required" supported, does not render control not supported supported, sets class="invalid" if false supported, used for rendering repeats supported, used for rendering repeats not supported not supported supported not supported dom no supported, no client side processing properly implemented, i think only those functions supported by libXML's xpath implementation supported supported supported supported supported not supported supported supported supported supported supported supported supported supported xml:lang not supported class supported navIndex not supported accessKey supported supported supported supported, creates field label not supported supported, creates "title" (rollover) not supported not supported supported not supported supported, startIndex and number attributes not supported no cursors supported not supported not supported not supported For obvious reasons, the options supported are limited due to browser limitations. http supported https supported mailto not supported file not supported post not supported get supported put not supported form-data-post supported urlencoded-post supported