1.1 --- a/README.txt Thu Jul 14 22:54:44 2005 +0000
1.2 +++ b/README.txt Fri Jul 15 13:19:25 2005 +0000
1.3 @@ -1,36 +1,36 @@
1.4 Warnings:
1.5
1.6 - * Mozilla/Firefox will not allow the XMLHttpRequest in-page updates to
1.7 - function unless the application URL defined within the Configurator
1.8 - application (and other relevant applications) matches the URL at which
1.9 - the browser finds the application.
1.10 + * Various browsers (eg. Mozilla/Firefox, Konqueror) will not allow the
1.11 + XMLHttpRequest in-page updates to function unless the application URL
1.12 + defined within the Configurator application (and other relevant
1.13 + applications) matches the URL at which the browser finds the application.
1.14
1.15 --------
1.16
1.17 Steps for making a new application:
1.18
1.19 - 1. Design a template, adding forms and fields. In the beginning, it is not
1.20 - that important to use the correct names in each of the fields - these
1.21 - will be added later.
1.22 + 1. Design a template, adding forms and fields. In the beginning, it is not
1.23 + that important to use the correct names in each of the fields - these
1.24 + will be added later.
1.25
1.26 - 2. Add structural template attributes such as template:element,
1.27 - template:attribute and template:value so that the fields sit in
1.28 - different parts of the input document format being modelled. Replace
1.29 - the field names with special functions such as template:field-name().
1.30 - For buttons which add and remove parts of the input document, employ
1.31 - selector notation and the template:this-position() function.
1.32 + 2. Add structural template attributes such as template:element,
1.33 + template:attribute and template:value so that the fields sit in different
1.34 + parts of the input document format being modelled. Replace the field
1.35 + names with special functions such as template:field-name(). For buttons
1.36 + which add and remove parts of the input document, employ selector
1.37 + notation and the template:this-position() function.
1.38
1.39 - 3. Where multiple choice fields are employed, input documents must be
1.40 - transformed so that the multiple choice options are included in the
1.41 - output. This can be achieved using documents containing the different
1.42 - option values and transformations which insert those values into the
1.43 - input document.
1.44 + 3. Where multiple choice fields are employed, input documents must be
1.45 + transformed so that the multiple choice options are included in the
1.46 + output. This can be achieved using documents containing the different
1.47 + option values and transformations which insert those values into the
1.48 + input document.
1.49
1.50 - 4. To produce the output document, the template needs preparing first so
1.51 - that an output stylesheet is produced; then, the output stylesheet is
1.52 - applied to the processed input document utilising various extension
1.53 - functions which produce the computed field names in the final output
1.54 - document.
1.55 + 4. To produce the output document, the template needs preparing first so
1.56 + that an output stylesheet is produced; then, the output stylesheet is
1.57 + applied to the processed input document utilising various extension
1.58 + functions which produce the computed field names in the final output
1.59 + document.
1.60
1.61 Recommendations:
1.62