XML Schema "lum_button.xsd"
Target Namespace:
http://www.lumis.com.br/douicontrols/lum_button
Components:
2 local elements, 7 complexTypes
Schema Location:
E:\hudson\jobs\lpjava-6.1.x-dist\workspace\Lumis_PortalJava\Lumis_PortalJava\distribution\tmp\lumis\doui\control\button\lum_button.xsd, see XML source
Includes Schema:
douibasecontrol.xsd [src]
Imported by Schema:
douicontrolsdefinition.xsd [src]
All Element Summary
image (type xsd:string)
Type:
xsd:string
Content:
simple
Defined:
locally at 5 locations
onClick (type onClientEvent)
Type:
onClientEvent
Content:
complex, 4 attributes, 10 elements
Defined:
locally at 5 locations
Complex Type Summary
lum_addButton
Content:
complex, 5 attributes, 2 elements
Includes:
definitions of 2 attributes and 2 elements
Used:
at 1 location
lum_autoAdminListButtons
Content:
complex, 9 attributes, 99 elements
Includes:
definitions of 5 attributes
Used:
at 2 locations
lum_button
Content:
complex, 4 attributes, 2 elements
Includes:
definitions of 1 attribute and 2 elements
Used:
at 5 locations
lum_buttonList
Content:
complex, 8 attributes, 99 elements
Includes:
definitions of 4 attributes
Used:
at 1 location
lum_deleteButton
Content:
complex, 6 attributes, 2 elements
Includes:
definitions of 3 attributes and 2 elements
Used:
at 1 location
lum_editButton
Content:
complex, 7 attributes, 2 elements
Includes:
definitions of 4 attributes and 2 elements
Used:
at 1 location
lum_lockButton
Content:
complex, 4 attributes, 2 elements
Includes:
definitions of 1 attribute and 2 elements
Used:
at 1 location
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Revision: 12049 $ $Date: 2010-10-27 15:08:45 -0200 (Wed, 27 Oct 2010) $ -->
<xsd:schema elementFormDefault="unqualified" targetNamespace="http://www.lumis.com.br/douicontrols/lum_button" xmlns="http://www.lumis.com.br/douicontrols/lum_button" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:include schemaLocation="../douibasecontrol.xsd"/>
<xsd:complexType name="lum_button">
<xsd:complexContent>
<xsd:extension base="lum_dataBoundControl">
<xsd:sequence>
<xsd:element minOccurs="0" name="image" type="xsd:string"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="onClick" type="onClientEvent"/>
</xsd:sequence>
<xsd:attribute name="text" type="xsd:string" use="optional"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_addButton">
<xsd:complexContent>
<xsd:extension base="lum_dataBoundControl">
<xsd:sequence minOccurs="0">
<xsd:element default="lumis/portal/client/images/Add.gif" minOccurs="0" name="image" type="xsd:string"/>
<xsd:element minOccurs="0" name="onClick" type="onClientEvent"/>
</xsd:sequence>
<xsd:attribute default="STR_ADD" name="text" type="xsd:string" use="optional"/>
<xsd:attribute name="interfaceId" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
By default the add interface opened when you press this button will use the following rules in precedence order:
1)Interface Id explicitly in as an attribute
2)Interface (if exists) with id = "add"+currentInterfaceId with first letter in upper case. e.g. if the current interface is administration, the interface calculated will be addAdministration
3)Interface (if exists) with id = "add"

If none of these rules apply, the button control will remove itself from its parent.
If the destination interface has been placed within a page of the portal, this button will redirect to that page.
If the destination interface has not been placed in a page, the button will open a popup page with the given interface mounted run-time.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_lockButton">
<xsd:complexContent>
<xsd:extension base="lum_dataBoundControl">
<xsd:sequence minOccurs="0">
<xsd:element default="lumis/portal/client/images/Lock.gif" minOccurs="0" name="image" type="xsd:string">
<xsd:annotation>
<xsd:documentation>image of the button</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="onClick" type="onClientEvent"/>
</xsd:sequence>
<xsd:attribute default="STR_LOCK" name="text" type="xsd:string" use="optional"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_editButton">
<xsd:complexContent>
<xsd:extension base="lum_dataBoundControl">
<xsd:sequence minOccurs="0">
<xsd:element default="lumis/portal/client/images/Edit.gif" minOccurs="0" name="image" type="xsd:string"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="onClick" type="onClientEvent"/>
</xsd:sequence>
<xsd:attribute default="STR_EDIT" name="text" type="xsd:string" use="optional"/>
<xsd:attribute name="interfaceId" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
By default the edit interface opened when you press this button will use the following rules in precedence order:
1)Interface Id explicitly in as an attribute
2)Interface (if exists) with id = "edit"+currentInterfaceId with first letter in upper case. e.g. if the current interface is administration, the interface calculated will be editAdministration
3)Interface (if exists) with id = "edit"

If none of these rules apply, the button control will remove itself from its parent.
If the destination interface has been placed within a page of the portal, this button will redirect to that page.
If the destination interface has not been placed in a page, the button will open a popup page with the given interface mounted run-time.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="listControlId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Identifier of the list control that this button is associated to. If not specified the id of the first control of type advancedTabularData in the interface is used.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="parameterId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
By default the edit button passes the primary key value with a parameter name as the field id. If you want to change the name of the parameter that is being passed to the edit property page, set this value to the desired name.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_deleteButton">
<xsd:complexContent>
<xsd:extension base="lum_dataBoundControl">
<xsd:sequence minOccurs="0">
<xsd:element default="lumis/portal/client/images/Delete.gif" minOccurs="0" name="image" type="xsd:string">
<xsd:annotation>
<xsd:documentation>image of the button</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="onClick" type="onClientEvent"/>
</xsd:sequence>
<xsd:attribute default="STR_DELETE" name="text" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
text that will be displayed within the button. Default value is STR_DELETE (translated to the current language)
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="delete" name="processActionId" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
identifier of the process action that should be called when this button is pressed.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="listControlId" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
identifier of the list control that the delete process action should take its item to delete values from.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_buttonList">
<xsd:complexContent>
<xsd:extension base="lum_control">
<xsd:attribute default="LumButton1" name="listId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Id that will be placed in the div that represents this button list. This id is generally used to control visualization via .css
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="align" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
controls alignment of buttons. One possible value is "right"
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="false" name="isVertical" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
defines whether the controls within this list are vertially positioned.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="true" name="spacer" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
specifies whether there should be a spacer between the buttons.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_autoAdminListButtons">
<xsd:complexContent>
<xsd:extension base="lum_control">
<xsd:attribute name="addInterfaceId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Interface that should be opened when the add button is pressed.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="editInterfaceId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Interface that should be opened when the edit button is pressed.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="delete" name="deleteProcessActionId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Process action Id that should be called when the delete button is pressed.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="lock" name="lockProcessActionId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Process action Id that should be called when the (un)lock button is pressed.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="configureInterfaceId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Interface that should be opened when the configure button is pressed.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>
XML Schema documentation generated with DocFlex/XML (Kit) v1.6.2
DocFlex/XML is a powerful template-driven documentation and report generator from any data stored in XML files. Based on an innovative technology developed by FILIGRIS WORKS, this new tool offers virtuoso data querying and formatting capabilities not found in anything else!
Need to convert your XML data into a clear nice-looking documentation or reports? Web-ready hypertext HTML or printable MS Word / OpenOffice.org friendly RTF? DocFlex/XML may be a cheap, quick and effective solution exactly for this task!
Have questions? Not sure how to use it? Just send us e-mail to contact@filigris.com and we are always happy to help you! See also our services at www.filigris.com

Lumisportal  STR_VERSION - STR_COPYRIGHT