WidgetPublisher:waHTML
Use valid xhtml (it can be Strict or Transitional). XML validity is very important due to node manipulations on certain host platforms.
Class Attributes are used to define node names, as getElementById is not supported by various platforms. There are also special Class Attributes with a specific role.
By default, links are loaded inside the widget, and override the content of the ldWidgetContent node.
Use the hash sign to specify the destination node; for example nextpage.htm#myNodeName will load nextpage.htm inside the first node whose class attribute is myNodeName.
In order to load a link outside of the widget, use the target attribute "_blank".
It is also possible to refresh a specific node or set of nodes inside the widget, by including the ldWidgetRefresh tag in the file called by ajax. In this case, the framework will match the nodes contained in the widget with the nodes contained in the file called by ajax, using the className identifier. All matched nodes will be updated (innerHTML and link attributes). This is especially useful when refreshing the widget.
All preferences are automatically appended to all internal links (ajax calls) as get parameters. There is no need to include them.
If you use a form, use the GET method as much as possible, and use only one button per form (the value of the button will not be sent).If you need to use the POST method, for example if you need to allow submission of files, please note that the framework will react as follows:
A special feature of our API is the ability to store preferences from the widget. In order to do so, add the following attributes to the input tag:
Standard inline Javascript is not supported on many host platforms. For this reason, waJS should be used.
Do not use CSS stylesheets (use inline style attributes in HTML code only)