-
15. Re: RichFaces Future. Plans for the next 6 months
oak3 Jul 26, 2008 5:25 PM (in response to sergeysmirnov)For me the best new feature would be a lot of new different examples and a lot of very good documentation... I believe this is a key to success for your library, and would be really happy to try more different examples. As of new components, the only one you really need i think is rich text editor and you are allready working on it which is good :) So imho you should focus more on performance improvements and quality of components. Again more different examples would help you to improve existing components.
-
16. Re: RichFaces Future. Plans for the next 6 months
dansouza Aug 22, 2008 2:03 PM (in response to sergeysmirnov)Another component nice to have: something similar to Tomahawk Schedule. The idea behind that component it's great, but it's not so stable!
Best regards,
Daniel -
17. Re: RichFaces Future. Plans for the next 6 months
nbelaevski Aug 24, 2008 2:05 PM (in response to sergeysmirnov)Hello all,
Once again, here is the link to add your wishes or vote for them: http://wiki.jboss.org/wiki/RichFacesFuture . -
18. Re: RichFaces Future. Plans for the next 6 months
cyberanto Aug 25, 2008 3:43 PM (in response to sergeysmirnov)When I tried to edit the page, I got an error like POST not allowed for this page ...
Highest on my list would be a table component with paging features like the ones in ADF ... the data table scroller in place now is considered 'weird' by our users, and does not work very well with large datasets
Richfaces has lots of great features, please add a more 'professional' looking table (or maybe a short tutorial on how to skin it?)
Thanks"nbelaevski" wrote:
Hello all,
Once again, here is the link to add your wishes or vote for them: http://wiki.jboss.org/wiki/RichFacesFuture . -
19. Re: RichFaces Future. Plans for the next 6 months
pmaedel Sep 3, 2008 10:44 AM (in response to sergeysmirnov)Im thinking of a simple feature that would improve usability and looks of UI:
Components should be able to specify other componentIds within an equalWidth attribute which will lead to render both of the components with the same width, that being the width of the widest component of all components specified within the attribute.<h:panelGrid columns="2"> <h:outputText value="press button one:"/> <a4j:commandButton id="longBtn" value="Loooooooooooooooooooooooong Button Text" equalWidth="shortBtn"/> <h:outputText value="press button two:"/> <a4j:commandButton id="shortBtn" value="Short Button Text" equalWidth="longBtn"/> </h:panelGrid>
What you say?