• 1
• 2
• 3
• 4
• 5

action actions ajax april asp attribute august btnsay button called class classes click client code components control create december descriptor descriptors div element email event events exposed exposes february form function handling head html http id instance january javascript july june label lblhello mapped march microsoft november october page part properties property propertykey raised rss runat script scripts september server service setpropertyaction side span string tag tags target text tutorial type xml

Keyword Cloud Navigation Map

In the first part of this tutorial on xml-script we introduced type descriptors and learned how to read them. In this second part we'll see how to declaratively handle events raised by client side controls.

Handling events

When talking about type descriptors in the first part of the tutorial, we stated that exposing a descriptor allows instantiating client side components using xml-script. Just by looking at the type descriptor of a class, we could get an idea of how the xml-script needed to create an instance, should look. For example, the Sys.Preview.UI.Button and the Sys.Preview.UI.Label classes contained in the PreviewScript.js file expose the following descriptors:

Sys.Preview.UI.Button.descriptor = {
  properties: [ { name: 'command', type: String },
                { name: 'argument', type: String } ],
  events: [ { name: 'click' } ]
}
Sys.Preview.UI.Label.descriptor = {
  properties: [ { name: 'htmlEncode', type: Boolean },
                { name: 'text', type: String } ]
}

All the information we need to write the code in the following example is contained in the above descriptors. The code, based on the standard structure of an xml-script block of code, creates an instance of both the Button and the Label classes and wires the click event of the button with a JavaScript function that displays a message on the label.

Read Full Tutorial...