NOTE: This page is a work in progress for the version 3.10 of Orbeon Forms. Scheduled featuresForm Builder / Form Runner
Issues that need fixing before release[Updated 2011-10-21] Blockers
Other issuesMajor cosmeticCompatibility notesForm Runner persistence layer configurationIn 3.9, you had a direct mapping from app, form, form type to the URI implementing the REST persistence API. For instance, to map "everything" to the Oracle persistence layer, in 3.9 you would write:<property as="xs:anyURI" name="oxf.fr.persistence.app.uri.*.*.*" value="/fr/service/oracle"/>3.10 introduces a level of indirection: you map app, form, form type to a provider, and then map that provider to its REST persistence API. Since a provider named oracle is pre-defined, the configuration equivalent to the above 3.9 property is:<property as="xs:string" name="oxf.fr.persistence.provider.*.*.*" value="oracle"/>Amongst other things, this allows you to setup Orbeon Forms to use different schemas for different app, form, and form type combination. For instance you could store everything related to an hr app in once schema and everything related to another finance app in another schema. For more on this, see how to setup the persistence layer for multiple schemas.Similarly, for eXist:
Here is the 3.8/3.9 way of configuring the URI to point to the eXist location:
And here is the 3.10 property:
Form Runner references to attachmentsUp to Orbeon Forms 3.9, form definitions and form data referenced attachments including the persistence implementation provider. For example, the path to an attached image would look like:
This caused issues if you need to change persistence providers but want to keep the same data. Post-3.9, the specific persistence implementation name is replaced by a generic and local persistence path:
URLs to a specific provider still exist, but they now require specific configuration headers and typically will no longer work correctly to load attachments. This means that you may need to convert paths in your existing data to adapt to the new scheme. Form Builder components configurationThe following property was deprecated and has been removed:
Instead, use oxf.fb.toolbox.group. See also Configuration Properties - Form Builder.Error handling during XForms processingError handing is more permissive, to allow users to recover from a crash in more cases. See XForms - XPath and Actions Error Handling for more information about the new behavior. Look and feel of Form Runner buttonsThe fr:button component provides nice-looking cross-browser buttons by using the underlying YUI button widget. However with older browsers, the JavaScript involved can make page loading slower than desirable when a large DOM and/or large number of butons are present.In this version of Orbeon Forms, we have made the default button produced by xf:trigger look nice out of the box, and without JavaScript. This means that you usually won't need fr:button at all.Form Funner and Form Builder have been updated to use xf:trigger instead of fr:button. The CSS for the new buttons is available in xforms.css.Removal of xforms-widgets.xslThe xforms-widgets.xsl transform was deprecated in Orbeon Forms 3.8 and has been removed.Follow the 3.8 release notes linked above for how to transition to using <fr:tabview> instead.The preferred version of implementing new components is by using XBL. Removal of widget:xforms-instance-inspectorThe component <widget:xforms-instance-inspector> was deprecated in Orbeon Forms 3.8 and has been removed. Instead, use:
NOTE: You don't need the namespace mapping if you already have it in scope. Renaming of oxf:xhtml-rewrite and oxf:html-rewrite inputs and outputsThese processors' inputs and outputs are renamed as follows:
This is consistent with most processors. NOTE: These processors are unlikely to be used outside of Orbeon Forms internals. |
|
|
|
Orbeon Forms "next" |