Miscellaneous"

From Documentation
m ((via JWB))
m
Line 3: Line 3:
 
= Button: use the <code>os</code> mold if there are a lot of buttons =
 
= Button: use the <code>os</code> mold if there are a lot of buttons =
  
The <code>trendy</code> mold of a button provides a better and consistent look for, especially, Internet Explorer 6. Unfortunately, the browser (particularly, Internet Explorer) will be slowed down if there are a lot of button (with <code>trendy</code>) in the same page.
+
The <code>trendy</code> mold of a button provides a better and more consistent look, especially for Internet Explorer 6. Unfortunately, the browser (particularly, Internet Explorer) will be slowed down if there are a lot of buttons (with <code>trendy</code>) in the same page.
  
  Notice that the default mold is <code>os</code> in ZK 5, while <code>trendy</code> in ZK 3.6. Since ZK 7.0.0, there is no difference between <code>os</code> and <code>trendy</code>.
+
  Notice that the default mold is <code>os</code> in ZK 5, while <code>trendy</code> in ZK 3.6.
 +
{{versionSince | 7.0.0}} There is no difference between <code>os</code> and <code>trendy</code>.
  
 
The default mold can be changed easily. For example,
 
The default mold can be changed easily. For example,

Revision as of 03:04, 2 February 2024

Button: use the os mold if there are a lot of buttons

The trendy mold of a button provides a better and more consistent look, especially for Internet Explorer 6. Unfortunately, the browser (particularly, Internet Explorer) will be slowed down if there are a lot of buttons (with trendy) in the same page.

Notice that the default mold is os in ZK 5, while trendy in ZK 3.6.
Since  7.0.0 There is no difference between os and trendy.

The default mold can be changed easily. For example,

<library-property>
	<name>org.zkoss.zul.Button.mold</name>
	<value>trendy</value>
</library-property>

Refer to ZK Configuration Reference for more information.

Prolong the Period to Check Whether a File Is Modified

ZK caches the parsed result of a ZUML page and re-compiles it only if it is modified. In a production system, ZUML pages are rarely modified so you can prolong the period to check whether a page is modified by specifying file-check-period in WEB-INF/zk.xml as shown below. By default, it is 5 seconds.

<desktop-config>
    <file-check-period>600</file-check-period><!-- unit: seconds -->
</desktop-config>

Version History

Version Date Content
     



Last Update : 2024/02/02

Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.