that makes good sense, its all in the documentation, sorry for wasting your time
On Fri, Apr 22, 2016 at 4:23 PM, Dan Haywood <[email protected]> wrote: > No, for a fieldset the actions are listed first, because these are the ones > associated with the fieldset itself (on the top panel). After that come > the properties. Each property can, within it, list its actions; these are > rendered below the property or to the side of it. > > Hope that makes sense > > Dan > > > On 22 April 2016 at 04:21, Stephen Cameron <[email protected]> > wrote: > > > Hi, > > > > Another thing I noted is that currently the component.xsd schema says you > > have to add all tns:action then all tns:property then metadataError > > elements in a sequence. > > > > If the order of properties and actions should be more flexible, as I > assume > > it should, you need a xs:choice, I think the following is correct. > > > > <xs:complexType name="fieldSet"> > > <xs:sequence> > > <xs:choice maxOccurs="unbounded"> > > <xs:element ref="tns:action" /> > > <xs:element ref="tns:property" /> > > </xs:choice> > > <xs:element minOccurs="0" name="metadataError" > type="xs:string" > > /> > > </xs:sequence> > > <xs:attribute name="name" type="xs:string" use="required" /> > > <xs:attribute name="id" type="xs:string" /> > > <xs:attribute name="unreferencedActions" type="xs:boolean" /> > > <xs:attribute name="unreferencedProperties" type="xs:boolean" /> > > </xs:complexType> > > >
