-
1. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
viggo.navarsete Aug 12, 2007 6:03 AM (in response to viggo.navarsete)Update. The calendar is actually skinned correctly! It's only the panel that isn't!
-
2. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
viggo.navarsete Aug 16, 2007 4:32 AM (in response to viggo.navarsete)Anyone having the same problem? That is, the header of the Panel isn't skinned?
-
3. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
ilya_shaikovsky Aug 16, 2007 5:02 AM (in response to viggo.navarsete)hm.. looks like environment or code problems. please give us more info
-
4. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
viggo.navarsete Aug 16, 2007 5:10 AM (in response to viggo.navarsete)Here's the JSP:
<%@page contentType="text/html"%> <%@page pageEncoding="UTF-8"%> <%@taglib prefix="f" uri="http://java.sun.com/jsf/core"%> <%@taglib prefix="h" uri="http://java.sun.com/jsf/html"%> <!-- Richfaces taglibrary --> <%@ taglib uri="http://richfaces.ajax4jsf.org/rich" prefix="rich"%> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <title>JSP Page</title> </head> <body> <f:view> <rich:panel> <f:facet name="header"> Write your own custom rich components with built-in AJAX support </f:facet> text.... </rich:panel> <rich:simpleTogglePanel switchType="client" label="Add AJAX capability to existing JSF applications"> context... </rich:simpleTogglePanel> </f:view> </body> </html>
I'm running the latest code 3.1.0-SNAPSHOT source code from the repository, both ajax4jsf and richfaces. The strange thing is that the header of the simpleTogglePanel looks ok.
Please tell if I can provide more information about my project/environment! -
5. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
viggo.navarsete Aug 16, 2007 11:10 PM (in response to viggo.navarsete)Hi ilya_shaikovsky, did you understand why I didn't get the header correct?
-
6. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
ilya_shaikovsky Aug 20, 2007 5:29 AM (in response to viggo.navarsete)Sorry, lost your post :( What about JSF and facelets libraries versions
-
7. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
viggo.navarsete Aug 20, 2007 6:11 AM (in response to viggo.navarsete)I'm running JSF RI 1.2. How can I determine the facelets library version?
-
8. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
ilya_shaikovsky Aug 20, 2007 6:25 AM (in response to viggo.navarsete)Sorry.. seems you didn't use it. What about to wrap your plain code to f:verbatim?
-
9. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
viggo.navarsete Aug 20, 2007 8:09 AM (in response to viggo.navarsete)It didn't help wrapping it into a f:verbatim tag:
<rich:panel> <f:facet name="header"> Write your own custom rich components with built-in AJAX support </f:facet> text.... </rich:panel> </f:verbatim>
-
10. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
viggo.navarsete Aug 20, 2007 8:10 AM (in response to viggo.navarsete)sorry, forgot the start f:verbatim. Here's the code
<f:verbatim> <rich:panel> <f:facet name="header"> Write your own custom rich components with built-in AJAX support </f:facet> text.... </rich:panel> </f:verbatim>
-
11. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
viggo.navarsete Aug 20, 2007 8:12 AM (in response to viggo.navarsete)I could perhaps add that the code is running on Glassfish, could that be a problem? I've had problems deploying my JSF application to a JBoss 4.2.x AS, and haven't had time to look into that problem yet.
-
12. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
ilya_shaikovsky Aug 20, 2007 8:44 AM (in response to viggo.navarsete)I mean verbatim around plain text such as "Write your own custom rich components with built-in AJAX support"
-
13. Re: Panel and calendar isn't skinned when using the 3.1.0.SN
viggo.navarsete Aug 20, 2007 8:51 AM (in response to viggo.navarsete)that's better:) Now it's ok:)
Thanks a lot for your great support!!!