RichFaces 4.0: DataTable sorting/filtering feature

[abelevich]

     There are some sorting/filtering implementation specific questions which I want to discuss:

• Should we provide built-in sorting/filtering in the  DataTable in the RF-4.0? Currently there is no built-in sorting exist. We provide only current component visual state via visual model (see DataTable visual models implementation discussion for the details ).  User should implement sorting/filtering by himself. During meeting discussion were proposed next ways of implementation sorting/filtering feature:

• Write integration code for different DAO frameworks instead of built-in sorting.
• Implement built-in sorter by default or setter FOR custom sort feature ( for example, to store in SQL "SORT BY" or Hibernate criteria ).

     Thoughts are welcome!

         

[abelevich]

up: see IRC meeting log in attachment for details

[nbelaevski]

To start with, consider looking at the following issue, submitted by end developer: https://jira.jboss.org/jira/browse/RF-8269

[abelevich]

nbelaevski wrote:

To start with, consider looking at the following issue, submitted by end developer: https://jira.jboss.org/jira/browse/RF-8269

ok

[konstantin.mishin]

About second point of this issue: Method modify() is called two times per live-circle. First time for decoding request. Second time for encoding response.

[abelevich]

abelevich wrote:

nbelaevski wrote:

To start with, consider looking at the following issue, submitted by end developer: https://jira.jboss.org/jira/browse/RF-8269

ok

      I've looked through this issue good point which we should add to requirements is customizable sorting/filtering data order.  I think this is good feature must be implemented. As for the first point we have already considered this feature.

[abelevich]

Should we implement separate sorting/filtering controls (I mean new JSF components like ToggleControl) for the sorting/filtering features?

[jbalunas]

Based on our conversation today in IRC we have the beginings of a plan to address this and some of the items in the jira issue above.

I'm all for having an API that supports a good deal of custumization and enhancements.  My only concern ( and I brought it up in the chat ) is about make the default usability easy to get started with.

Once you get the summary of the chat today up in wiki or discussion form we'll review more.

[abelevich]

[e-mail] wrote:

Based on our conversation today in IRC we have the beginings of a plan to address this and some of the items in the jira issue above.

I'm all for having an API that supports a good deal of custumization and enhancements.  My only concern ( and I brought it up in the chat ) is about make the default usability easy to get started with.

Once you get the summary of the chat today up in wiki or discussion form we'll review more.

ok.  I had a discussion with Pavel yesterday about how to better implement toggler control which could be support various toggling types in various RichFaces components (e.g. expand/collapse in the SubTable, sorting in the DataTable etc.), . He provided an interesting view about component interaction via Richfaces event API. I am going to use this technics to prototype toggle controls for the sorting and when if all will be fine use this in the SubTable toggle control.