[richfaces-issues] [JBoss JIRA] Assigned: (RF-259) Improved table support

[Nick Belaevski (JIRA)]

     [ http://jira.jboss.com/jira/browse/RF-259?page=all ]

Nick Belaevski reassigned RF-259:
---------------------------------

    Assignee: Ilya Shaikovsky  (was: Nick Belaevski)

Please review features requested

> Improved table support
> ----------------------
>
>                 Key: RF-259
>                 URL: http://jira.jboss.com/jira/browse/RF-259
>             Project: RichFaces
>          Issue Type: Feature Request
>    Affects Versions: 3.0.0
>            Reporter: Joseph Marques
>         Assigned To: Ilya Shaikovsky
>             Fix For: 3.2.0
>
>
> the assumption made for all of the following feature requests is that we're dealing with hundreds of thousands of objects to be displayed in tabular form, so any solutions that accommodate the requested functionality must be able to re-render the table component too (so as to tell the underlying paged-at-a-time data model to go fetch another data page from the backing store, similar to something like http://wiki.apache.org/myfaces/WorkingWithLargeTables ):
> * hook up a drop-down list to the table that enables users to change the number of records displayed in the table (updates the 'rows' attribute of the rich:dataTable) and re-renders the table
> * enhanced sorting support - maintain the current sort column and ordering (ASC or DESC), allow the results to be sorted by clicking on the column header, and re-render the table after the click.  also, support two graphic icons that you can add to the beginning or end of the column name to indicate whether that column is currently sorted ASC or DESC - this would be implicitly part of the renderer for the column header
> ** note: an event model alone would probably not be enough for this solution because you'd need to be able to render the table column based off of the current state of the sort - so this would likely require an extension to the table component model itself to support this related state data
> * integrate check boxes / radio buttons into the table, and have client-side actions taken as a result of selections / deselections (can click the 'clone' button if exactly one row is selected, can click the 'compare' button if exactly two rows are selected, can 'delete' rows regardless of how many are selected), then be able to easily/conveniently pass this selected list along with the submission of the form

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira