The embed Element"
| Line 27: | Line 27: | ||
=Link to a JavaScript File = | =Link to a JavaScript File = | ||
| − | Notice that you need to specify your '''application context path''' in the source path. | + | Notice that you need to specify your '''application context path''' in the source path. Becuase ZK directly puts the content into a response without any encoding. |
<source lang='xml' highlight='4'> | <source lang='xml' highlight='4'> | ||
<device-config> | <device-config> | ||
| Line 36: | Line 36: | ||
</device-config> | </device-config> | ||
</source> | </source> | ||
| − | |||
=Version History= | =Version History= | ||
Revision as of 03:45, 28 June 2022
Syntax:
<embed>any_valid_fragment</embed>
[Optional][Multiple]
It specifies the content that shall be added to the output generated and sent to the client when rendering a desktop. The syntax of the content will depend on the client. For Ajax clients, it can be any tags that can be placed inside HTML <head>, such as <script>, <meta> and others.
This can be a way to include a javascript code snippet in all pages, e.g. a javascript patch or a custom widget javascript. For example, if you want to show the progress bar in the center of the browser window, you can specify the following:
<device-config>
<device-type>ajax</device-type>
<embed><![CDATA[
<script type="text/javascript">
AU_progressbar = function (id, msg) {
Boot_progressbox(id, msg, 0, 0, true, true);
};
</script>
]]></embed>
</device-config>
You can specify multiple embed elements and their content be concatenated together.
Link to a JavaScript File
Notice that you need to specify your application context path in the source path. Becuase ZK directly puts the content into a response without any encoding.
<device-config>
<device-type>ajax</device-type>
<embed><![CDATA[
<script type="text/javascript" src="/myapp/zkpatch/lisbox_selectbugfixed.js"></script>
]]></embed>
</device-config>
Version History
| Version | Date | Content |
|---|---|---|