RE: A few XForms Questions...

Hi Dan,
  
> In fact, other common ways to present this are an expandle/collapsible
> tree or a categorized icon bar (popularized by Outlook). A tree
> containing checkboxes could be used for a selectMany. (The categorized
> bar does not need icons.)

> The point is there are many representations. In my XForms implementation,
> I will probably extend the selectUI attribute to them to our designers
needs.

We have had similar thoughts, but the problem is that selectUI is defined
as:

  <xsd:attribute name="selectUI" use="optional">
    <xsd:simpleType>
      <xsd:restriction base="xsd:string">
        <xsd:enumeration value="radio"/>
        <xsd:enumeration value="checkbox"/>
        <xsd:enumeration value="menu"/>
        <xsd:enumeration value="listbox"/>
        <xsd:enumeration value="combo"/>
      </xsd:restriction>
    </xsd:simpleType>
  </xsd:attribute>

Putting aside the 'combo' value, which I assume should be removed, does
anyone know why it wasn't defined as:

  <xsd:attribute name="selectUI" use="optional">
    <xsd:simpleType>
      <xsd:union memberTypes="xforms:QNameButNotNCNAME">
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:enumeration value="radio"/>
            <xsd:enumeration value="checkbox"/>
            <xsd:enumeration value="menu"/>
            <xsd:enumeration value="listbox"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:union>
    </xsd:simpleType>
  </xsd:attribute>

Whilst we're on the subject, why can't selectUI be applied to other form
controls? Since it is only defined as a 'hint' anyway, then why not give
'hints' wherever you want to?

Regards,

Mark


Mark Birbeck
Managing Director
x-port.net Ltd.
4 Pear Tree Court
London
EC1R 0DS

E: Mark.Birbeck@x-port.net
W: www.x-port.net
T: +44 (20) 7689 9232
Co-author Professional XML and
Professional XML Meta Data,
both by Wrox Press

Received on Friday, 17 May 2002 20:04:57 UTC