Namespace: |
|
Type: |
|
Content: |
simple, 5 attributes |
Defined: |
globally within component.xsd, see XML source |
Used: |
at 4 locations |
XML Representation Summary |
|||||
<inline |
|||||
forms | = |
list of xsd:string |
|||
id | = |
xsd:string |
|||
ifEvents | = |
list of xsd:string |
|||
ifExpr | = |
xsd:string |
|||
scope | = |
xsd:string : "function" |
|||
> |
|||||
|
|||||
</inline> |
Type Derivation Summary xsd:string ![]() ![]() |
Derivation: |
<xsd:element name="inline"> <xsd:annotation> <xsd:documentation> Provide Javascript in-line with templates and other sourceGen elements. Be sure to supply a "forms" attribute, otherwise the code may execute multiple times during the source generation contribution-gathering phase. </xsd:documentation> </xsd:annotation> <xsd:complexType> <xsd:simpleContent> <xsd:annotation> <xsd:documentation> Tells where the inline code appears. By default, it appears in the primary function into which templates are generated, thus is executed in line with them. Specifying "file" or "prototype" means the content is intended to modify the Javascript prototype, thus it is placed at the top level of the file. ${jsObject}.prototype may be used to access the prototype. Note: include() and includeFrom() calls should be placed in the prototype scope, or their contents will not be visible to derived components. Added post 1.1: "file" is a synonym for "prototype". </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Added post 1.1: the identifier for the inline section, which makes it inheritable. Inline sections are inherited as templates, accessible with "useTemplate" of the same id. If unspecified, a default id is assigned. Use a blank id to avoid inheriting. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:simpleContent> </xsd:complexType> </xsd:element> |
Type: |
|
Use: |
optional |
Defined: |
Type: |
xsd:string |
Use: |
optional |
Defined: |
locally, within this element |
<xsd:attribute name="id" type="xsd:string" use="optional"> <xsd:annotation> <xsd:documentation> Added post 1.1: the identifier for the inline section, which makes it inheritable. Inline sections are inherited as templates, accessible with "useTemplate" of the same id. If unspecified, a default id is assigned. Use a blank id to avoid inheriting. </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
|
Use: |
optional |
Defined: |
Type: |
xsd:string |
Use: |
optional |
Defined: |
Type: |
xsd:string |
Use: |
optional |
Default: |
"function" |
Defined: |
locally, within this element |
<xsd:attribute default="function" name="scope" type="xsd:string" use="optional"> <xsd:annotation> <xsd:documentation> Tells where the inline code appears. By default, it appears in the primary function into which templates are generated, thus is executed in line with them. Specifying "file" or "prototype" means the content is intended to modify the Javascript prototype, thus it is placed at the top level of the file. ${jsObject}.prototype may be used to access the prototype. Note: include() and includeFrom() calls should be placed in the prototype scope, or their contents will not be visible to derived components. Added post 1.1: "file" is a synonym for "prototype". </xsd:documentation> </xsd:annotation> </xsd:attribute> |