| Both sides previous revision Previous revision Next revision | Previous revision |
| docs:3500:0800:0830 [2023/04/05 07:03] – sean | docs:3500:0800:0830 [2025/06/12 04:00] (current) – Change to AwareIM aware_support3 |
|---|
| Just like with queries, the parser object represents the form controller and the "markup" object represents the HTML markup of the form. However, there is a significant difference in the "config" object exposed by forms. Whereas for queries the "config" object represents some widget of the Kendo UI library, that is mainly responsible for the implementation of the query, there is no such widget for forms. A form is just an HTML code that consists of rows and columns of the Bootstrap grid system ([[http://getbootstrap.com/css/|]]). Each row and column contains attributes of the form – depending on the type of the attribute they are either implemented as plain HTML or they may also include a configuration for a Kendo UI widget. | Just like with queries, the parser object represents the form controller and the "markup" object represents the HTML markup of the form. However, there is a significant difference in the "config" object exposed by forms. Whereas for queries the "config" object represents some widget of the Kendo UI library, that is mainly responsible for the implementation of the query, there is no such widget for forms. A form is just an HTML code that consists of rows and columns of the Bootstrap grid system ([[http://getbootstrap.com/css/|]]). Each row and column contains attributes of the form – depending on the type of the attribute they are either implemented as plain HTML or they may also include a configuration for a Kendo UI widget. |
| |
| This HTML is also wrapped in a "panel" that includes HTML of toolbars around the form (if they are defined) and also the implementation of the default or custom panel header. Note that the HTML that includes toolbars and panel header is also included as part of the query markup. | This HTML is also wrapped in a "panel" that includes HTML of toolbars around the form (if they are defined) and also the implementation of the default or custom panel header. Note that the HTML that includes toolbars and panel header is also included as part of the form markup. |
| |
| So the "config" object for forms represents the configuration of a special Aware IM object called "panel". You can find the code of this object in ''AwareIM/Tomcat/webapps/AwareIM/aware_kendo/panel.js'' file. At the beginning of the file there is a description of all configturation parameters supported by this object. You can change these parameters by your script.. | So the "config" object for forms represents the configuration of a special AwareIM object called "panel". You can find the code of this object in ''AwareIM/Tomcat/webapps/AwareIM/aware_kendo/panel.js'' file. At the beginning of the file there is a description of all configturation parameters supported by this object. You can change these parameters by your script.. |
| |
| For example, the following script will turn off the display of the header for the form, no matter what is specified in the //**Aware IM**// properties of the form: | For example, the following script will turn off the display of the header for the form, no matter what is specified in the //**AwareIM**// properties of the form: |
| |
| <code javascript>config.preventHeader = true;</code> | <code javascript>config.preventHeader = true;</code> |
| |
| However, you are unlikely to need it because most of these parameters can be customized in //**Aware IM**// without having to use a script. | However, you are unlikely to need it because most of these parameters can be customized in //**AwareIM**// without having to use a script. |
| |
| You may, however, want to modify the markup of the form – for example, you may want to modify the generated layout or styling of some attributes. You can use it through the "markup" object (or in the "render" script after the form has been drawn). The description of the HTML markup is beyond the scope of this document. If you want to study it you can just generate a form and use the browser inspector to display the HTML of the form. You can then use your scripts to modify this markup. | You may, however, want to modify the markup of the form – for example, you may want to modify the generated layout or styling of some attributes. You can use it through the "markup" object (or in the "render" script after the form has been drawn). The description of the HTML markup is beyond the scope of this document. If you want to study it you can just generate a form and use the browser inspector to display the HTML of the form. You can then use your scripts to modify this markup. |