diff --git a/Documentation/forms-intro.html b/Documentation/forms-intro.html index 63a9a7be1..cb2e0066a 100644 --- a/Documentation/forms-intro.html +++ b/Documentation/forms-intro.html @@ -93,9 +93,11 @@ } table.parameters { background-color: #dddddd; + margin-left: 4em; } /* background-color: #ddddff; */ table.properties { background-color: #ddddff; + margin-left: 4em; } /* background-color: #ddddff; */ td { padding: 0.5em; @@ -240,20 +242,17 @@

Form field types

- - - - - - + + + + + +
labelString A label for the form field. This is the prompt for the user, e.g., - "Name", "Employer". + "Name", "Employer". If the label is not given in the form, the + system will make one from a label of the property in the ontology.
propertyrdf:Property When the user enters the data, it is stored in the web as a triple with this property as its predicate. @@ -262,9 +261,7 @@

Form field types

default[according to field type] Optional The input control is set to this value by default. It is easiest for the user to enter this value. (This value is not automatically @@ -272,6 +269,17 @@

Form field types

some way.
suppressEmptyUneditableBoolean + Setting this flag (on a single form field not a structure) means that when the user is just reading the data, not + editing it, the fields with blank data will be removed completely. + This avoid things like a blank field for a region in an address when there isn't one given. + This can make the UX much cleaner. Defaults to false. +

@@ -399,6 +407,24 @@

Group

the same as for Form.

+ + + + + + + + + + + + +
weightxsd:integer0:lighter than normal, 1: Normal, 2,3: heavier than normal
partsrdf:Collection + The form fields, forms, in the group +
+ + +

Choice

The user choses an item from a class.

@@ -425,9 +451,7 @@

Choice

canMintNew - xsd:Boolean - If the user doesn't find the thing they want, can they introduce an item of that class by filling in a form about it? [Boolean] @@ -435,8 +459,8 @@

Choice

- If a new thing is minted, that will be done with a form which is a - ui:creationForm for the class. +

If a new thing is minted, that will be done with a form which is a + ui:creationForm for the class.

Multiple

@@ -454,6 +478,37 @@

Multiple

form. It is the field, or the address, and so on.

+ + + + + + + + + + + + + + + + + + + + + + +
orderedBooleanIf true, the user has an ordered array of things, and the data is in an RDF collection. + If false, the UI is irrelevant and the data is a series of arcs.
propertyrdf:PropertyThe API details or query endpoint and query details to be used to search the item in + the databasse.
reverseBooleanIf set, the form will write data triple like X P S instead of the normal S P X. +
partFormThe form to be used for each one. +
+ + + +

Classifier

@@ -468,7 +523,7 @@

Classifier

- +

This form field leverages the ontology heavily. It pulls the subclasses of the given class, and makes a pop-up menu for the user to chose one. If and only if the ontology says that the class is a disjoint union @@ -477,7 +532,7 @@

Classifier

shows that that subclass has its own subclasses, then the user will be prompted to pick one of those, to (if they like) further refine the selection. And so on. - +

The classifier pops a menu to allow the user to select a set of values to classify the subject. @@ -517,7 +572,7 @@

Options

- and for each case: +

and for each case:

@@ -565,24 +620,21 @@

Autocomplete

- + - - - - + of AutocompleteField to share the same DataSource, by specifying different values for targetClass.
labelPropertyStringrdf:Property The property which will be used to store the name of the selected thing as a separate triple
dataSourceDataSourceThe API details or query endpint and query details to be usde to search of the itemn in the databasse.
targetClass rdfs:ClassIs tyhis is specified, it be used to replace any occuurences of + Is tyhis is specified, it be used to replace any occurrences of "$(targetClass)" in the query template. this allows different instances - of AutocompleteField to share the same DatSource, by specifying different values for targetClass.
@@ -604,8 +656,17 @@

Heading

The text content of the heading + + suppressIfUneditable + Boolean + If data is uneditable,ie read-only mode, hide this comment + +

The suppressIfUneditable flag allow you to make a form which + is much cleaner and simpler when the user is just reading information, + not editing it.

+

Comment

@@ -618,11 +679,16 @@

Comment

contents String - The text content of the comment. (This should be displayed by form systems as pre-wrap mode.) + + suppressIfUneditable + Boolean + If data is uneditable,ie read-only mode, hide this comment + + @@ -634,9 +700,11 @@

Conclusion

daily life at home and at work. It can be vary efficient as developers can reuse material between forms. Users can even generate their own forms.

+

Future directions include separate implementations of the form UI code in for various platforms, and using various UI frameworks. There may also be extensions of the system with new field types, more options for setting style from various sources, etc. +

diff --git a/Documentation/talks/FormsTalk.html b/Documentation/talks/FormsTalk.html index 0d3618d91..5a22df66d 100644 --- a/Documentation/talks/FormsTalk.html +++ b/Documentation/talks/FormsTalk.html @@ -165,10 +165,10 @@

Single Line Text field

Examples of other form fields

    -
  1. Examples of individual Form Fields
  2. -
  3. Examples of structures in forms: Groups
  4. -
  5. Selection, Options, Autocomplete
  6. -
  7. Examples of a Solid profile editing form
  8. +
  9. Examples of individual Form Fields
  10. +
  11. Examples of structures in forms: Groups
  12. +
  13. Selection, Options, Autocomplete
  14. +
  15. Examples of a Solid profile editing form