for starter, what new components are added:
Technically, we have created the 3.0 set using our new Component Factory (Ajax4jsf Component Development Kit). It was not so much different what to do - new component or re-factor the old one. On the priority bases, some of the old components are moved to the next release or removed
To your list:
dialog window was based on the iframe and has it own conversation context. So, it has to be re-factored to be flexible. For example, to use Seam Conversation context
panel menu, menu, calendar need to be refactoring toward improving their models
speedometer. Such component should developed as a complete set of industrial-like components.
debug components. a4j:log from ajax4jsf core library has the similar behavior. We have a plan to have more sophisticated client-side monitor of the server-side data.
header components. Ie. h1, h2, h3, h4, h5, h6. As soon as facelets as well as jsf 1.2 allow to use just pure html h1-h6, those header components just do not make any sense
Thank you very much, SergeySmirnov:
It's a good message.
Hope richfaces become stronger and stronger!
And hope can see the next release soon. ^_^
What about the skin issue? will it be possible to customize the skin as in v 2.0?
We are especially missing the round corner option:
In general, the skins are expendable. You can create your own skin and have what even parameters you want there.
We refused the idea to have a cornered panels, because the components with heavy layout are killers for Ajax (the traffic issue).
I also wrote about it here: