click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Malcolm Edgar (JIRA)" <>
Subject [JIRA] Commented: (CLK-501) Add first class support for HTML Head resources such as Javascript and CSS
Date Tue, 10 Mar 2009 00:09:11 GMT


Malcolm Edgar commented on CLK-501:

In terms of a design we could introduce a HTML Element class which can be used for:
* TitleElement
* CssStyleElement
* CssImportElement
* JsScriptElement
* JsImportElement

A Page could expose the methods:

List<Element> getHeadElements()

List<Element> getJsElements()

In the page template users would do something like:
#foreach ($element in $headElements)

#foreach ($element in $jsElements)

> Add first class support for HTML Head resources such as Javascript and CSS
> --------------------------------------------------------------------------
>                 Key: CLK-501
>                 URL:
>             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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message