JBossDeveloper

It would be great to implement some kind of scroller in rich:tabPanel - if there are many tabs it doesn't look good.
There might be some max width given for the tabPanel and all the tabs that don't fit can be seen using some kind of scroll.. hope I made it clear :)

Or there's a way to implement this kind of functionality for the tabPanel?

Yep, exactly something like tab scroller in extjs. Can it be implemented?

everything can be implemented. The question is how easy it might be done.

I suggest, it should be two buttons (ajax or not) where you can manipulate with 'rendered' attribute of the rich:tabs in the action or action listeners of those buttons .

I think this feature is badly needed also. If the extjs scrollable tabs is difficult to implement, it could just be a DHTML iframe something like this

http://picasaweb.google.co.uk/richard.fanning/General

What you think? (Sorry about the link had nowhere else to upload)

Thanks

Rich

Yep, that would be great - kind of drop down list with labels of those tabs that don't fit.

First of all, thanks to Sergey for sponsoring this important discussion and for doing such good work.

I come into this discussion as both a developer and potential Red Hat investor.

As a developer, I can tell you I am in dire need of several components that have been mentioned already:

I find very important

- Breadcrumbs
- Sortable data table
- File upload progressbar

I miss a breadcrumbs component in RichFaces. We use breadcrumbs in each web application, but I didn't find so far any capable breadcrumbs components. There is one in the Trinidad, but we cann't share it with our environment ! Please, provide this component in the next release.

Thanks.
Oleg.

I forgot to say: sortable data table should expect comparator classes to use already completed comparators for the sorting capability. For example:

<rich:column comparator=#{mybean.mycomparator}>...</rich:column>
or
<rich:column comparatorId="mycomparatorId">...</rich:column>

As far as I know, the MyFaces Tomahawk allows sortable data tables, but doesn't support own comparators.

"ova" wrote:
I find very important

- Breadcrumbs
- Sortable data table
- File upload progressbar

I miss a breadcrumbs component in RichFaces. We use breadcrumbs in each web application, but I didn't find so far any capable breadcrumbs components. There is one in the Trinidad, but we cann't share it with our environment ! Please, provide this component in the next release.

Thanks.
Oleg.

"SergeySmirnov" wrote:

"henrik.lindberg" wrote:
Although it is great to get more components and features. Our main problems have to do with quality, performance, diagnostics, and debugging.

what methodology you use for diagnostics and debugging.

RichFaces in the short-term future. What is your vision?

<f:view>
 <x:comp1 header-style="portlet-section-header" inset-style="portlet-section-text" tooltip="#{lookup(me.id)}" value="first" />
 <x:comp1 header-style="portlet-section-header" inset-style="portlet-section-text" tooltip="#{lookup(me.id)}" value="second" />
 ...
 <x:manyMoreComponents />
 </f:view>

<x:default attribute="comp1.header-style" value="portlet-section-header" />
 <x:default attribute="comp1.inset-style" value="portlet-section-text" />
 <x:default attribute="comp1.tooltip" value="#{lookup(me.id)}" />

 <f:view>
 <x:comp1 value="first" />
 <x:comp1 value="second" />
 <x:manyMoreComponents />
 </f:view>

<x:defaults>
 comp1 {
 header-style: portlet-section-header;
 inset-style: portlet-section-text;
 tooltip: #lookup(me.id)
 }
</x:defaults>

"SergeySmirnov" wrote:
Update: the overview is on the wiki - [url]
What do you thing about it? What do you expect from the RichFaces in the future? We are open to discuss now.

"SergeySmirnov" wrote:

"damianharvey" wrote:

How about a carousel based on something like this http://zend.lojcomm.com.br/icarousel/example3.asp

Such kind of components I can create by myself with CDK in one or two days without even bothering our developer team (Like I did with rich:effect). However, I am afraid people start to complain that we produce "toys", but not the real components.

"bruno.arruda" wrote:
I also think that the examples should always have a SIMPLEST version, I mean, if you look at the examples, most of them uses facelets, managed beans, advanced attributes, i think for the begginers user it might be a little confusing and hard-working... So I think that shold be samples that shows the core functions with maximum simplicty. Like a evolution of the livedemo page.