[
https://issues.apache.org/jira/browse/WICKET-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Rantalaiho updated WICKET-1192:
------------------------------------
Fix Version/s: (was: 1.4-M4)
1.5-M1
Sounds like a good idea but better to only fix in 1.5 to keep 1.4 more
1.3-compatible.
> move static factory methods off of HeaderContributer and onto related classes
> -----------------------------------------------------------------------------
>
> Key: WICKET-1192
> URL: https://issues.apache.org/jira/browse/WICKET-1192
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Ryan Sonnek
> Priority: Minor
> Fix For: 1.5-M1
>
>
> The "static utility" pattern of the HeaderContributor class should be
> improved by moving the methods off of HeaderContributor and onto the relevant
> classes.
> this is very important for long term "plugability" of the framework.
> Currently, it is not possible for an external project like wicketstuff to add
> a new HeaderContribution in this "standard/supported" wicket API. The wicket
> FeedResource API is an example of this.
> http://www.jroller.com/wireframe/entry/wicket_feedresource
> for example, the method HeaderContributor.forJavascript() should move to
> JavascxriptResource.headerContribution(). This API is much easier for
> developers to discover by looking up the relevant class (JavascriptResource)
> instead of digging through tutorials to find the "magical" HeaderContributor.
> mailing list conversation:
> http://www.nabble.com/-RFE--HeaderContributor.forFavicon%28Reference%29-tf4896178.html#a14035092
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
