[jbalunas]

Also I think we should keep paging logic in component, and not in view bean, otherwise we will need it to update visual model when paging is used.

Could the same be said of sorting?

[jbalunas]

"value" - component does in-memory processing, "processedValue" - subset of data prepared according to rules from visual model.

/me Thinking if there is a way to make this easier at the view end....

It now seems we are talking about 3 "values".

Could this be handled using inheritance and/or decorator patterns to simplify....

/me just brainstorming.

[nbelaevski]

Also I think we should keep paging logic in component, and not in view bean, otherwise we will need it to update visual model when paging is used.

Could the same be said of sorting?

I think no. Most of the outcome of paging logic is used by component. For example, if we take some existing solution: Query, we see that there are attributes that are vital for rich:dataScroller like "nextExists", "previousExists" or "firstResult". Also there are "order", "queryParameterValues" attributes, but component(s) can live without them, because these attributes can be set by view bean when model is created (e.g. we can provide a set of classes transforming visual model objects into another well-known to end-developer objects like Crank or EJB Criteria).

Also data scroller component should be able to correct current page according to rows count handling situations when current page is not in a range of pages existing in model. That's what sorting doesn't require.

[nbelaevski]

"value" - component does in-memory processing, "processedValue" - subset of data prepared according to rules from visual model.

/me Thinking if there is a way to make this easier at the view end....

It now seems we are talking about 3 "values".

Could this be handled using inheritance and/or decorator patterns to simplify....

/me just brainstorming.

Yes, different value attributes don't seem a good approach. Inheritance or decorator pattern may work, but the I see the problem here is how to let component getting all necessary information without making very complex and custom to RF data models.

[abelevich]

Hi, I've implemented a little part of the dataTable visualModel support.
You could find sources and samples here:

sources: https://anonsvn.jboss.org/repos/richfaces/root/ui-sandbox/trunk/components/tables/ui and
sample: https://anonsvn.jboss.org/repos/richfaces/root/examples-sandbox/trunk/components/tables

note then now only subTable attribute "expanded" saved in the SubTable visualModel. Please take a look and tell me if I am not on the right way.

[abelevich]

Should we provide built-in sorting/filtering in the  DataTable in the RF-4.0?

[abelevich]

abelevich wrote:

Should we provide built-in sorting/filtering in the DataTable in the RF-4.0?

discussion moved to the separate thread