Author: jacopoc
Date: Sat Nov 10 23:21:34 2007 New Revision: 593852 URL: http://svn.apache.org/viewvc?rev=593852&view=rev Log: Updated from trunk rev. 593786 Modified: ofbiz/site/dtds/widget-form.xsd Modified: ofbiz/site/dtds/widget-form.xsd URL: http://svn.apache.org/viewvc/ofbiz/site/dtds/widget-form.xsd?rev=593852&r1=593851&r2=593852&view=diff ============================================================================== --- ofbiz/site/dtds/widget-form.xsd (original) +++ ofbiz/site/dtds/widget-form.xsd Sat Nov 10 23:21:34 2007 @@ -190,13 +190,13 @@ </xs:attribute> <xs:attribute type="xs:string" name="header-row-style"> <xs:annotation><xs:documentation>The header-row-style specifies the style to use in the header of table.</xs:documentation></xs:annotation> - </xs:attribute> + </xs:attribute> <xs:attribute type="xs:string" name="default-table-style"> <xs:annotation><xs:documentation>The default-table-style specifies the style to use in the table.</xs:documentation></xs:annotation> </xs:attribute> <!-- not sure this is such a good idea <xs:attribute type="xs:string" name="hidden-values-map-name"> - <xs:annotation><xs:documentation>A map that contains hidden field name/value pairs. + <xs:annotation><xs:documentation>A map that contains hidden field name/value pairs. The reason for this is to eliminate the need to code custom forms so that auxiliary, passthru data can be sent to the server. By doing it this way, more standard forms can be used. </xs:documentation></xs:annotation> @@ -211,6 +211,7 @@ <xs:attributeGroup name="attlist.alt-target"> <xs:attribute type="xs:string" name="use-when" use="required"/> <xs:attribute type="xs:string" name="target"/> + <xs:attribute type="xs:string" name="target-type"/> </xs:attributeGroup> <xs:element name="auto-fields-service"> <xs:complexType> @@ -305,7 +306,7 @@ <xs:attributeGroup name="attlist.sort-field"> <xs:attribute type="xs:string" name="name" use="required"/> </xs:attributeGroup> - + <!-- ================== FIELDS ==================== --> <xs:element name="AllFields" abstract="true"/> <xs:element name="field"> @@ -453,7 +454,7 @@ <xs:element name="date-time" substitutionGroup="AllFields"> <xs:annotation> <xs:documentation> - A special entry for date-time fields; may just have a default size text + A special entry for date-time fields; may just have a default size text entry box and some sort of widget to make date entry/selection easier. </xs:documentation> </xs:annotation> @@ -829,6 +830,7 @@ <xs:enumeration value="like"/> <xs:enumeration value="contains"/> <xs:enumeration value="empty"/> + <xs:enumeration value="notEqual"/> </xs:restriction> </xs:simpleType> </xs:attribute> @@ -937,8 +939,8 @@ <xs:attribute type="xs:string" name="list-entry-name"> <xs:annotation> <xs:documentation> - If specified the list entry will be placed in the local - context, otherwise each list entry must be a Map that will be expanded + If specified the list entry will be placed in the local + context, otherwise each list entry must be a Map that will be expanded into the local context. </xs:documentation> </xs:annotation> @@ -946,7 +948,7 @@ <xs:attribute type="xs:string" name="key-name" use="required"> <xs:annotation> <xs:documentation> - The value of the key-name will be the value passed + The value of the key-name will be the value passed to the server; this should be the full name of the location of the key value in the context, given the list-entry-name or expanded list-entry Map as the options you would most likely use. @@ -1080,6 +1082,7 @@ <xs:attribute type="xs:string" name="field" use="required"/> <xs:attribute type="xs:string" name="from-field"/> <xs:attribute type="xs:string" name="value"/> + <xs:attribute type="xs:string" name="default-value"/> <xs:attribute name="global" default="false"> <xs:simpleType> <xs:restriction base="xs:token"> |
Free forum by Nabble | Edit this page |