Gregory,
First, thanks for the switch/case/toggle stylesheet. I will defer to Alex the task to look at it.
> 1) If I need to pass the filled out instance data in XML format and > session data to a servlet/JSP on another server how can I accomplish > this from within the Orbeon environment?
You could do this with an HTTP POST (which we cannot do right now without writing a custom processor, but we have been planning to include this for a while). You could also use a regular Web service, with the Delegation processor.
If the Servlet / JSP was in the same Servlet container, you could use the Scope serializer to store the XML document into the Servlet request object, and then forward the request to that Servlet / JSP.
> 2) When I initially present the instance data with bound required > attributes (using the bind element in the model data) to the client > how do I prevent the page from showing errors until after they > attempt to submit (or at least until they have had the opportunity > to fill in the required fields)?
You can set an xxforms:show-errors attribute on an xforms:group element. If it is present and has value "false", errors won't show. There is an example of this in the BizDoc example, where the value of this attribute is set with XSLT.
> 3) Can the intermediate solution to the input label be included in > the released war file?
Not sure what you mean by this, but every change to the source that is checked in should make it to the "unstable" builds on SourceForge:
http://orbeon.sourceforge.net/unstable-blds/presentation-server/
> 4) Per Micah Dubinko, who contributed to the XForms specification, > the CSS3 entry: > > @namespace xforms url(http://www.w3.org/2002/xforms/); > /* Display a red asterisk after all required form controls */ > *:required::after {content: red; color:red;} > > should function with an xforms implementation. Obviously, I have > tried this and had no success. Is there some way to accomplish this > in Orbeon's servlet? At the very least would it be possible to pass > along CSS attributes (class="") for xforms elements within the > servlet?
Once the HTML code reaches your web browser, it no longer has any XForms in it. So, of course, the CSS doesn't match on any element with an xforms namespace.
What you could do though, is, in xforms-to-xhtml.xsl, annotate specially the required fields. You could directly add the "*", or annotate the XHTML produced, and then style it in theme.xsl.
> 5) I also notice that no events (other than submit) seem to be > supported, will more be included in the future?
This would be nice, but we don't have any ETA at the moment.
> 6) The Chiba implementation has a simple chart that demonstrates > what elements of the XForms 1.0 specification have been implemented, > those which are partially implemented, and those which are not yet > implemented would it be possible for Orbeon to provide something > similar? Our choice of Orbeon is based almost entirely on the > licensing arrangement (LGPL vs Artistic) so the > implemented/not-implemented feature list would be VERY helpful.
This is a good idea. I entered an RFE for this:
http://sourceforge.net/tracker/index.php?func=detail&aid=1055427&group_id=116683&atid=675663
This said, the reference is currently the XForms Reference documentation page. What's not in there is not supposed to be implemented.
In case it is not clear for everybody: at the moment, we only support a subset of the XForms 1.0 specification. We are aiming at supporting more and more of the specification over time.
> 7) Erik Bruchez has a bug, 1052268, posted regarding multiple > instances in an XForms model. Is there any estimate as to when this > may be addressed?
No ETA at the moment, unfortunately.
> 8) The itemset element does not appear to be in the > xforms-to-xhtml.xsl but it has been indicated previously that > itemset is implemented in the Presentation Server. Where might this > implementation be?
Another question for Alex. I cannot see the implementation either.
-Erik
Gregory Blajian wrote:
> Hi, > > I am trying quite hard to work with this (the Orbeon Presentation > Server) but am finding the limitations to be difficult to overcome. > First, I have a not so robust contribution to suggest for the > XForms UI element switch/case/toggle (included at the end of the e-mail). > It works pretty well in IE but causes "issues" in Mozilla and Opera based > browsers, it seems to cause the page to reload if the switches are nested. > I would also point out that Orbeon complained xforms:switch is not in the > xforms namespace, thus the gbxforms namespace, but it is defined in > section 9.2 in the XForms 1.0 final specification. > Second, in response to Rahul Agarwal's question regarding > javascript 2004 Oct 26, I found the following worked fine through the > Orbeon processor: > > <xhtml:script type="text/javascript" > src="currentOrbeonPath/myjscript.js"/> <!-- where currentOrbeonPath is > the relative servlet file path to your js --> > > Finally, I get to my questions. > 1) If I need to pass the filled out instance data in XML format > and session data to a servlet/JSP on another server how can I accomplish > this from within the Orbeon environment? > 2) When I initially present the instance data with bound required > attributes (using the bind element in the model data) to the client how do > I prevent the page from showing errors until after they attempt to submit > (or at least until they have had the opportunity to fill in the required > fields)? > 3) Can the intermediate solution to the input label be included in > the released war file? > 4) Per Micah Dubinko, who contributed to the XForms specification, > the CSS3 entry: > > @namespace xforms url(http://www.w3.org/2002/xforms/); > /* Display a red asterisk after all required form controls */ > *:required::after {content: red; color:red;} > > should function with an xforms implementation. Obviously, I have tried > this and had no success. Is there some way to accomplish this in Orbeon's > servlet? At the very least would it be possible to pass along CSS > attributes (class="") for xforms elements within the servlet? > 5) I also notice that no events (other than submit) seem to be > supported, will more be included in the future? > 6) The Chiba implementation has a simple chart that demonstrates > what elements of the XForms 1.0 specification have been implemented, those > which are partially implemented, and those which are not yet implemented > would it be possible for Orbeon to provide something similar? Our choice > of Orbeon is based almost entirely on the licensing arrangement (LGPL vs > Artistic) so the implemented/not-implemented feature list would be VERY > helpful. > 7) Erik Bruchez has a bug, 1052268, posted regarding multiple > instances in an XForms model. Is there any estimate as to when this may > be addressed? > 8) The itemset element does not appear to be in the > xforms-to-xhtml.xsl but it has been indicated previously that itemset is > implemented in the Presentation Server. Where might this implementation > be? > > Well, that's about it. I hope someone can help me out with my > questions and that my couple of contributions prove useful to someone. > > Very Respectfully, > Gregory J Blajian > > > <!-- > /* original trigger template */ > <xsl:template match="xforms:trigger"> > /* < ! - - TODO - - > */ > <xsl:message terminate="yes">Trigger control is not > supported</xsl:message> > </xsl:template> > --> > > <!-- Greg Blajian 2004 Oct 25 > New trigger and switch templates > --> > <xsl:variable name="quot">'</xsl:variable> > <xsl:template match="gbxforms:trigger"> > <xsl:variable name="triggerId" select="@id"/> > <xsl:variable name="triggerLabel" select="xforms:label"/> > <xsl:variable name="triggerToggleCaseId" > select="gbxforms:action/gbxforms:toggle/@case"/> > <xsl:variable name="triggerToggleSwitchId" > select="gbxforms:action/gbxforms:toggle/@switch"/> > <button id="{$triggerId}" > onclick="switch_{$triggerToggleSwitchId}({$quot}{$triggerToggleCaseId}{$qu > ot});"> > <label><xsl:value-of > select="gbxforms:label"/></label> > </button> > </xsl:template> > > <xsl:template match="gbxforms:switch"> > <xsl:variable name="switchId" select="@id"/> > <script type="text/javascript"> > function switch_<xsl:value-of select="@id"/>(a) > { > <xsl:for-each select="gbxforms:case"> > <xsl:variable name="caseId" select="@id"/> > document.getElementById(<xsl:value-of > select="$quot"/><xsl:value-of select="@id"/><xsl:value-of > select="$quot"/>).className='dis2'; > </xsl:for-each> > document.getElementById(a).className='dis1'; > } > </script> > <xsl:for-each select="gbxforms:case"> > <xsl:variable name="caseId" select="@id"/> > <xsl:variable name="disp"> > <xsl:choose> > <xsl:when test="@selected = 'true' > or @selected='true()'">dis1</xsl:when> > > <xsl:otherwise>dis2</xsl:otherwise> > </xsl:choose> > </xsl:variable> > <div id="{$caseId}" class="{$disp}"> > <xsl:apply-templates/> > </div> > </xsl:for-each> > </xsl:template> > > <!-- > Since this probably won't work in this location > the css will also be added to the autopilot CSS page > --> > <xsl:template match="head/title"> > <xsl:copy-of select="."/> > <style type="text/css">.div{display:block;} > .dis2{display:none;}</style> > </xsl:template>
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
