-
1. Re: Custom CSS style for each row in rich:dataTable
bitec Oct 14, 2009 1:58 AM (in response to alextracer)Exactly the same problem. I want to apply the custom style to the row, and use <rich:columnGroup> for this, but all header facets disappear in this case... So, now I have to use styleClass for every cell, which looks a bit ugly. Can anyone from RF team explain this behaviour? Thanks.
-
2. Re: Custom CSS style for each row in rich:dataTable
nbelaevski Oct 14, 2009 7:09 AM (in response to alextracer)Hi,
Have you tried to put header/footer inside column?
Also there's rowClasses attribute. -
3. Re: Custom CSS style for each row in rich:dataTable
bitec Oct 14, 2009 10:35 AM (in response to alextracer)Hi, Nick.
This pattern does not show headers:<rich:columnGroup > <rich:column sortBy="#{selectedEntity.id}" styleClass="#{selectedEntity.status.styleClass}"> <f:facet name="header"> <h:outputText value="#{bundle.id}"/> </f:facet> <h:outputText value="#{selectedEntity.id}"/> </rich:column> </rich:columnGroup>
-
4. Re: Custom CSS style for each row in rich:dataTable
bitec Oct 14, 2009 10:38 AM (in response to alextracer)Forgot to write about rowClasses - I need the row color, depending on some properties of the current row. rowClasses do not provide this possibility, if I'm not mistaken.
-
5. Re: Custom CSS style for each row in rich:dataTable
liuliu Oct 15, 2009 10:44 AM (in response to alextracer)
i think rowClasses could accept a EL expression -
6. Re: Custom CSS style for each row in rich:dataTable
bitec Oct 15, 2009 11:01 AM (in response to alextracer)How should they look like "#{bean.getCommaSeparatedListOfStyles}"? Seems this atribute is evaluated once, not for each row and should return the static list of styles.
-
7. Re: Custom CSS style for each row in rich:dataTable
nbelaevski Oct 15, 2009 1:12 PM (in response to alextracer)"Bitec" wrote:
How should they look like "#{bean.getCommaSeparatedListOfStyles}"? Seems this atribute is evaluated once, not for each row and should return the static list of styles.
That's right. Looks like there is no easy solution for the problem.