Namespace: |
|
Content: |
complex, 6 attributes, 2 elements |
Defined: |
globally in lum_button.xsd, see XML source |
Includes: |
definitions of 5 attributes and 2 elements |
Used: |
at 1 location |
XML Representation Summary |
|||||
<... |
|||||
interfaceId | = |
xsd:string |
|||
isPrimary | = |
xsd:boolean : "false" |
|||
keepParentActive | = |
xsd:boolean : "false" |
|||
openRuntimeInterfaceBehavior | = |
("popup" | "replace" | "lightbox") |
|||
sourceId | = |
xsd:string |
|||
text | = |
xsd:string : "STR_ADD" |
|||
> |
|||||
|
|||||
</...> |
Type Derivation Tree lum_control lum_sourceBoundControl (extension) lum_addButton (extension) |
<xsd:complexType name="lum_addButton"> <xsd:complexContent> <xsd:sequence minOccurs="0"> <xsd:element default="lumis/portal/client/images/Add.gif" minOccurs="0" name="image" type="xsd:string"/> </xsd:sequence> <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:annotation> <xsd:documentation> <![CDATA[ By default, a "keepParentActive" attribute with value "false" is used on the onClick event for opening the destination interface for this add button. By specifying this attribute on the add button, it will be used when generating its onClick event. <p> For more information, see keepParentActive attribute on the onClick element. ]]> </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> <![CDATA[ By default no openRuntimeInterfaceBehavior on the onClick generated for the add button. If a value is specified in this attribute, it will be used on the onClick event for opening the destination interface for this add button. <p> For more information, see openRuntimeInterfaceBehavior attribute on the onClick element. ]]> </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Indicates whether the button is a primary button. Primary buttons are emphasized over non-primary buttons. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> |
Type: |
xsd:string |
Use: |
optional |
Defined: |
locally, within this complexType |
<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> |
Type: |
xsd:boolean |
Use: |
optional |
Default: |
"false" |
Defined: |
locally, within this complexType |
<xsd:attribute default="false" name="isPrimary" type="xsd:boolean" use="optional"> <xsd:annotation> <xsd:documentation> Indicates whether the button is a primary button. Primary buttons are emphasized over non-primary buttons. </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:boolean |
Use: |
optional |
Default: |
"false" |
Defined: |
locally, within this complexType |
<xsd:attribute default="false" name="keepParentActive" type="xsd:boolean"> <xsd:annotation> <xsd:documentation> <![CDATA[ By default, a "keepParentActive" attribute with value "false" is used on the onClick event for opening the destination interface for this add button. By specifying this attribute on the add button, it will be used when generating its onClick event. <p> For more information, see keepParentActive attribute on the onClick element. ]]> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
|
Use: |
optional |
Defined: |
locally, within this complexType |
<xsd:attribute name="openRuntimeInterfaceBehavior" type="openRuntimeInterfaceBehavior"> <xsd:annotation> <xsd:documentation> <![CDATA[ By default no openRuntimeInterfaceBehavior on the onClick generated for the add button. If a value is specified in this attribute, it will be used on the onClick event for opening the destination interface for this add button. <p> For more information, see openRuntimeInterfaceBehavior attribute on the onClick element. ]]> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:string |
Use: |
optional |
Default: |
"STR_ADD" |
Defined: |
locally, within this complexType |
<xsd:attribute default="STR_ADD" name="text" type="xsd:string" use="optional"/> |
Type: |
xsd:string, simple content |
Default: |
"lumis/portal/client/images/Add.gif" |
Defined: |
locally, within this complexType |
<xsd:element default="lumis/portal/client/images/Add.gif" minOccurs="0" name="image" type="xsd:string"/> |
Type: |
onClientEvent, complex content |
Defined: |
locally, within this complexType |
<xsd:element minOccurs="0" name="onClick" type="onClientEvent"/> |
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 14.0.0.210430 - Copyright © 2006–2021 Lumis EIP Tecnologia da Informação LTDA. All Rights Reserved.