script"
m |
m |
||
| Line 2: | Line 2: | ||
'''Syntax:''' | '''Syntax:''' | ||
| − | <?script type="text/javascript" [src="''uri''"] [charset="''encoding''"] | + | <?script [type="text/javascript"] [src="''uri''"] [charset="''encoding''"] |
| − | [content="javascript"] [if="..."] [unless="..."]?> | + | [content="''javascript snippet''"] [if="..."] [unless="..."]?> |
[since 3.6.2] | [since 3.6.2] | ||
| − | It specifies an element that shall be generated inside the HEAD element. It is generated ''after'' ZK default JavaScript and CSS files. Thus, it could override what is defined in ZK default JavaScript code. Currently only HTML-based clients (so-called browsers) support | + | It specifies an element that shall be generated inside the HEAD element. It is generated ''after'' ZK default JavaScript and CSS files. Thus, it could override what is defined in ZK default JavaScript code. Currently only HTML-based clients (so-called browsers) support it. Furthermore, HTML SCRIPT tag is actually generated for each of this declaration. |
| − | Developers can specify whatever attributes you like; it is up to the browser to interpret. ZK only evaluates the <code>if</code> and <code>unless</code> attributes, and encodes the URI of the <tt>href</tt> and <tt>src</tt> attribute (by use of | + | Developers can specify whatever attributes you like; it is up to the browser to interpret. ZK only evaluates the <code>if</code> and <code>unless</code> attributes, and encodes the URI of the <tt>href</tt> and <tt>src</tt> attribute (by use of by use of <javadoc method="encodeURL(java.lang.String)">org.zkoss.zk.ui.Execution</javadoc>). ZK generates all other attributes directly to the client. |
Notice that these header directives are effective only for the main ZUL page. In other words, they are ignored if a page is included by another pages or servlets. Also, they are ignored if the page is a <tt>zhtml</tt> file. | Notice that these header directives are effective only for the main ZUL page. In other words, they are ignored if a page is included by another pages or servlets. Also, they are ignored if the page is a <tt>zhtml</tt> file. | ||
<syntax lang="xml" > | <syntax lang="xml" > | ||
| − | <?script | + | <?script src="/js/foo.js"?> |
| − | <?script | + | <?script content="var foo = true; |
if (zk.ie) doSomething();"?> | if (zk.ie) doSomething();"?> | ||
Revision as of 04:35, 29 July 2011
Syntax:
<?script [type="text/javascript"] [src="uri"] [charset="encoding"] [content="javascript snippet"] [if="..."] [unless="..."]?>
[since 3.6.2]
It specifies an element that shall be generated inside the HEAD element. It is generated after ZK default JavaScript and CSS files. Thus, it could override what is defined in ZK default JavaScript code. Currently only HTML-based clients (so-called browsers) support it. Furthermore, HTML SCRIPT tag is actually generated for each of this declaration.
Developers can specify whatever attributes you like; it is up to the browser to interpret. ZK only evaluates the if and unless attributes, and encodes the URI of the href and src attribute (by use of by use of Execution.encodeURL(String)). ZK generates all other attributes directly to the client.
Notice that these header directives are effective only for the main ZUL page. In other words, they are ignored if a page is included by another pages or servlets. Also, they are ignored if the page is a zhtml file.
<syntax lang="xml" > <?script src="/js/foo.js"?> <?script content="var foo = true; if (zk.ie) doSomething();"?>
<window title="My App">
My content
</window>
</syntax>
As shown above, the attribute value could span multiple lines.
Alternatives
Alternatively, you could use the script component to embed JavaScript code. The script component supports more features such as defer, but it has some memory foot print at the server (since it is a component).
Version History
| Version | Date | Content |
|---|---|---|