[
https://issues.jboss.org/browse/RF-12537?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12537:
---------------------------------
Actually, as Adrian pointed out, ECSS and reslibs are supported, they are added to the
{{others}} collection of resources.
But that way priority and reslib expansion wouldn't be processed.
This would lead into pseudo-optimal state.
Resource Ordering -aware HeadRenderer
-------------------------------------
Key: RF-12537
URL:
https://issues.jboss.org/browse/RF-12537
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: core
Reporter: Lukáš Fryč
The order of resources rendered in a head is currently un-managed and can cause resource
ordering issues. (Which may be partially fixed by using different placement of
h:outputScript tags).
Furthermore a performance of application perceived by user might be significantly
enhanced when ordering head resources correctly (see Yahoo recommendations).
The proposal of {{HeadRenderer}} by Adrian Mitev:
https://gist.github.com/3899465
----
This proposal has several drawbacks:
* doesn't count with mime-types, depends on resource names (Resource provided by
ResourceHandler may be used here to obtain mime-type)
* resource names stored in attribute "name" are not part of JSF spec (afaik)
and thus implementation-dependent
* the implementation does not count with resource library notion (.reslib)
* ECSS is unsupported, but it can be simply changed with using ResourceHandler as
described above
Other than that the proposed solution seems like enough generic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira