The theme-uri-handler-class Element"
From Documentation
m (correct highlight (via JWB)) |
|||
Line 7: | Line 7: | ||
[Default: ''none''] | [Default: ''none''] | ||
− | It specifies the class to provide the theme (aka., a style sheet file) URI dynamically if you want to determine the theme based on the current user, cookie or locale. You can implement a class with the <javadoc type="interface">org.zkoss.zk.ui.util.ThemeURIHandler</javadoc> interface, and specify it with the < | + | It specifies the class to provide the theme (aka., a style sheet file) URI dynamically if you want to determine the theme based on the current user, cookie or locale. You can implement a class with the <javadoc type="interface">org.zkoss.zk.ui.util.ThemeURIHandler</javadoc> interface, and specify it with the <code>theme-uri-handler-class</code> element. Then, an instance of the class will be created. It will be called each time when a desktop is rendered to the client to determine the theme URI before ThemeProvider. |
Different from ThemeProvider, ThemeURIHandler is composable with other ThemeURIHandler. | Different from ThemeProvider, ThemeURIHandler is composable with other ThemeURIHandler. |
Latest revision as of 10:19, 19 January 2022
Since 9.6.0
Syntax:
<theme-uri-handler-class>a_class_name</theme-uri-handler-class>
[Default: none]
It specifies the class to provide the theme (aka., a style sheet file) URI dynamically if you want to determine the theme based on the current user, cookie or locale. You can implement a class with the ThemeURIHandler interface, and specify it with the theme-uri-handler-class
element. Then, an instance of the class will be created. It will be called each time when a desktop is rendered to the client to determine the theme URI before ThemeProvider.
Different from ThemeProvider, ThemeURIHandler is composable with other ThemeURIHandler.
Note: ThemeProvider still has the final decision. ThemeURIHandler will always be executed.
Version History
Version | Date | Content |
---|---|---|