Day 37th: Aurora Component Specification Summary _aurora Framework Learning

Aurora-framework's page structure is XML (extensible Identity language), which differs from HTML in that it is a language that focuses on the display of Web content and a language that focuses on page data transfer:

Data in XML if some special symbols can not be explained, this time to use, cdata[[]], put it in here, you can get an explanation, more in the script to use;

The hierarchy of the page structure:

----The outermost layer is <a:screen></a:screen>

----Middle tier

------<a:init-procedure></init-procedure>

-----<a:view></a:view> (Put data source and link layer and display layer)

-------<a:dataSets></a:dataSets> (data source and link layer)

----<a:dateSet></a:dateSet>

---<dates></dates>

--<a:record/>

----<fileds></fields>

---<field/>

------<a:screen-Body></a:screen-Body> (Display layer)

The head part must have <?xml version= "version number" encoding= "encoding"?>

1. The initials of all components are lowercase;

2.style in the use of the connection, the end of the time also used, the format unit px,dashed in Boreder equivalent to soild meaning

3. PX units cannot appear in non-style

4.textField for the meaning of the text field

5.prompt is the meaning of the attribute hint

6.maxLength is the length limit of the attribute

7.emptyText is the display text for the empty time

8.typeCase case is upper,lower, default lowercase

9.comboBox most commonly used component, in the screen file, define a ComboBox object, the id attribute of the dataset and the ComboBox Bindtarget

In contrast, the Fileld Name property of the dataset corresponds to the ComboBox's Name property so that the dataset is bound to the Commobox

Event in 10.events handler represents its own defined function functions, name indicates event type

11.bindtarget is the meaning of binding target, Bindmodel is the meaning of binding model, model can store the information of the database

12. When the connection layer field is defined, the value of the Optionfield is the part of the Id,displayfield value of the data source, and the value of Valuefield is the value corresponding to the values displayed. The value of the Returnfield corresponds to the return value selected in the displayfiled to the system background

13. Write Lov, the data source needs to use the attributes are: autopagesize automatic paging, Cansubmit can be submitted,

The properties used by the data link layer are

----Display section: Lovwidth,lovheight,lovlabelwidth,lovgridheight,title,require,requiredmessage

----Functional section: Autocomplete,autocompletefield,atuocompletesize,autolovquery

Mapping is the data source mapped to the link layer

Display domain Displayfield, range Valuefield, return domain Returnfield, these three levels can be omitted, replaced by the corresponding mapping attributes, essentially or from the data source map to the field name, and then through the display layer call

<a:mapping></a:mapping>

----<a:map from----to-----/>