ICEfaces
  1. ICEfaces
  2. ICE-9670

Add showcase ace:dataTable demo to demonstrate persistence of ace:tableConfigPanel user settings

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: 4.0.BETA, EE-3.3.0.GA_P02, 4.0
          • Component/s: Sample Apps
          • Labels:
            None
          • Environment:
            ICEfaces 3.x
          • Assignee Priority:
            P1
          • Affects:
            Sample App./Tutorial

            Description

            Using the ace:tableConfigPanel, users can configure their view on an ace:dataTable. User defined column settings (ordering, sorting and visibility) can optionally be persisted to backing-beans on the server for possible retention between sessions.

            This JIRA is to add a new demo to the ace:dataTable (ace:tableConfigPanel) showcase that demonstrates the technique of persisting the user settings and restoring them. The demo could have "Save", "Reset", and "Restore Save Settings" buttons.
             

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Arturo Zambrano added a comment - - edited

              r38703:
              Modified Table Configuration demo to show how to persist ace:tableConfigPanel settings.
              r38714:
              Modified Table Configuration demo for saving sorting order.

              Show
              Arturo Zambrano added a comment - - edited r38703: Modified Table Configuration demo to show how to persist ace:tableConfigPanel settings. r38714: Modified Table Configuration demo for saving sorting order.
              Hide
              Permalink
              Arturo Zambrano added a comment - - edited

              Added Advanced Table Configuration demo to show how to persist ace:tableConfigPanel settings when using multiple header rows.

              Show
              Arturo Zambrano added a comment - - edited Added Advanced Table Configuration demo to show how to persist ace:tableConfigPanel settings when using multiple header rows.
              Hide
              Permalink
              Arturo Zambrano added a comment -

              r38722:
              Committed fix for issue with not restoring original row order after removing custom sorting criteria; changed beans from session-scoped to window-scoped; added configurable settings to header columns.

              Regarding the issue with not restoring original row order after removing custom sorting criteria, the data model gets sorted when there's a sorting request with a custom ordering, but when all custom sort criteria are removed, the model is not sorted back to the original order, but simply left in the state it is at the moment. I tried setting a default order (sort only by id, ascending) when restoring to the default settings, but since this is done in the invoke application phase, the model doesn't get re-sorted, because the table does the sorting during decoding, initiated by a request. So what was done in the end was simply reset the model with the original data list when restoring defaults.

              Show
              Arturo Zambrano added a comment - r38722: Committed fix for issue with not restoring original row order after removing custom sorting criteria; changed beans from session-scoped to window-scoped; added configurable settings to header columns. Regarding the issue with not restoring original row order after removing custom sorting criteria, the data model gets sorted when there's a sorting request with a custom ordering, but when all custom sort criteria are removed, the model is not sorted back to the original order, but simply left in the state it is at the moment. I tried setting a default order (sort only by id, ascending) when restoring to the default settings, but since this is done in the invoke application phase, the model doesn't get re-sorted, because the table does the sorting during decoding, initiated by a request. So what was done in the end was simply reset the model with the original data list when restoring defaults.

                People

                • Assignee:
                  Arturo Zambrano
                  Reporter:
                  Ken Fyten
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: