[
http://issues.apache.org/click/browse/CLK-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11730#action_11730
]
Bob Schellink commented on CLK-501:
-----------------------------------
Hi Malcolm,
I like the idea of a more generic approach to HTML headers and housing these
classes in their own package.
How do you see Page and Control imports integrate though? For example will
#getHeadElements return the Control imports as well? Or will Control imports be
specified separately with the $cssIncludes and jsIncludes variables?
kind regards
bob
> Add first class support for HTML Head resources such as Javascript and CSS
> --------------------------------------------------------------------------
>
> Key: CLK-501
> URL: http://issues.apache.org/click/browse/CLK-501
> Project: Click
> Issue Type: New Feature
> Components: core
> Reporter: Bob Schellink
> Assignee: Bob Schellink
> Fix For: 2.1.0
>
>
> Currently Click supports HTML imports by overriding the method
> #getHtmlImports.
> This method is string based which makes it difficult to support advanced
> features such as templating, conditional imports, resource versioning etc.
> This feature request proposes to introduce first class HTML header resource
> classes including Javascript, JavascriptImport, CssImport and Css.
> Further a new method should be added to the Control interface: 'public List
> getHtmlHeaders' which returns a list of the Page or Control's HTML HEAD
> entries.
> This makes it possible to modify the Javascript and CSS imports without
> overriding a Control.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
