This is a follow-up to a discussion we had back in November last year:
http://www.nabble.com/Proposed-Xforms.js-change-tf2687543.html#a7494851Right now, xforms.js defines a number of global variables that you
might want to change:
var XFORMS_DELAY_BEFORE_INCREMENTAL_REQUEST_IN_MS = 500;
var XFORMS_DELAY_BEFORE_FORCE_INCREMENTAL_REQUEST_IN_MS = 2000;
var XFORMS_DELAY_BEFORE_ANY_REQUEST_IN_MS = 10;
var XFORMS_DELAY_BEFORE_DISPLAY_LOADING_IN_MS = 500;
var XFORMS_DEBUG_WINDOW_HEIGHT = 600;
var XFORMS_DEBUG_WINDOW_WIDTH = 300;
However you can't change those without modifying xforms.js for reasons
explained in
http://www.nabble.com/Proposed-Xforms.js-change-tf2687543.html#a7588269.
In addition, we have 2 global variables introduced by Ryan:
USER_LANGUAGE and FCK_CUSTOM_CONFIG. Those are not defined in
xforms.js but used in xforms.js. In this case it gives you an
opportunity of setting those outside of xforms.js.
The suggestion is that instead of using global variables, we would
have an API to set and get the value of those properties. We can make
that part of ORBEON.xforms.Document, since this is where we already
have 3 public APIs (dispatchEvent, getValue, and setValue). You could
set one of those properties in your code with:
ORBEON.xforms.Document.setProperty("delay-before-incremental-request-in-ms",
300);
The reason for making this lower case with dashes is to be consistent
with property names we have in config/properties.xml. One additional
step would be to allow those properties to be passed to the
client-side code when they are defined in config/properties.xml with:
<property as="xs:integer"
name="oxf.xforms.delay-before-incremental-request-in-ms" value="300"/>
Any comment?
Alex
--
Orbeon Forms - Web 2.0 Forms for the Enterprise
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
Locked
