[
https://issues.apache.org/jira/browse/WICKET-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514129
]
Eelco Hillenius commented on WICKET-771:
I'm wondering whether it is a good idea to grow the API even more, or just have
a slightly smarter way of determining keys. For instance, we could have a
class->string thingy somewhere for the purpose of creating shorter classnames.
If marking of header contributions would use this as well, and the libraries
that use the same libraries would register some root class with this (like
YuiLib in wicket-datetime) and reference their resources relative to that, they
could register such classes with the common name e.g. in the initializer of the
library.
pros: transparent, API doesn't grow, extends the idea of having those
class-string mappings
cons: another mechanism you'd have to learn, more magic.
WDYT? Matej? (since you've worked on this the last iterations).
> Provide ResourceReference with ID attribute for filtering multiple includes
> ---
>
> Key: WICKET-771
> URL: https://issues.apache.org/jira/browse/WICKET-771
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
>Affects Versions: 1.3.0-beta1, 1.3.0-beta2
>Reporter: Jim McLaughlin
> Fix For: 1.3.0-beta3
>
>
> Provide ResourceReference with an ID attribute that can be used to reduce
> multiple inclusions. This will allow different projects to include the same
> resources without worrying about double includes (if they agree to use the
> same id) even if the resources have different urls.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
