-
1. Re: Primefaces and richfaces features merged
Brian Leathem Jul 28, 2011 2:18 PM (in response to José Freitas)1 of 1 people found this helpfulWhy not just use the RichFaces CDK to wrap jQuery UI directly? Would make a neat project, and flex the muscle of the RichFaces CDK for sure!
-
2. Re: Primefaces and richfaces features merged
José Freitas Jul 28, 2011 4:56 PM (in response to Brian Leathem)Brian,
If we could use CDK to wrap jQueryUI and use themeroller on richfaces components that'd be a great step toward a happy end! cause we could use rich and prime faces in the same page without losing visual consistency, and I'd not need to use prime inputText for example, and then I could let primefaces handle just the non-core components.
-
3. Re: Primefaces and richfaces features merged
José Freitas Sep 30, 2011 2:12 PM (in response to José Freitas)Hey guys,
Some time a while ago I tried client validation system within a primefaces:inputText. It worked perfectly!
However the CVS don't work with primefaces:password component. That happens because the inputSecret is inside of a span tag (as a container).
and the p:password id will be the id of the span, not of the input. the input id would be something like ID_input (where ID is the value passed to id="" of the p:password).
I posted that on primefaces forums as primefaces issue, but they convinced me that it would be better to change richfaces. So we could make rf search by an input inside the component, not relaying only at the id, as it is today.
you can take a peek at my prime forum post in: http://forum.primefaces.org/viewtopic.php?f=3&t=15150
what do you think?
-
4. Re: Primefaces and richfaces features merged
Brian Leathem Sep 30, 2011 2:42 PM (in response to José Freitas)Sounds like a reasonable approach. Care to file a jira issue for this?