Details
-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 3.x, ace:dataTable
-
Support Case References:Support Case #12726 - https://icesoft.my.salesforce.com/5007000000adNJU
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
Description
In ICEfaces 3.0 the new ace:dataTable was added with a "liveScroll" feature that was, unfortunately, very limited in utility when combined with other ace:dataTable features, buggy, etc. As the "liveScroll" function was not up to ICEsoft's standard, it was deprecated as of ICEfaces 3.2.
This JIRA is to re-introduce support for a liveScroll functionality in a robust manner that will support its use in combination with all other ace:dataTable features.
The primary justification for a liveScroll feature is to provide "infinite" scalability to ace:dataTables that may be bound to very large datasets (e.g. 50K rows or much more).
To achieve this, it is necessary to dynamically "page" rows to the client browser as the user moves through the dataTable contents via the vertical scrollbar. Not only do rows need to be dynamically loaded or pre-loaded for the user, but rows must eventually also be dynamically removed from the browser DOM in order to prevent the eventual negative performance implications of an very large DOM in the browser, and the memory consumption that goes along with it.
This JIRA is to re-introduce support for a liveScroll functionality in a robust manner that will support its use in combination with all other ace:dataTable features.
The primary justification for a liveScroll feature is to provide "infinite" scalability to ace:dataTables that may be bound to very large datasets (e.g. 50K rows or much more).
To achieve this, it is necessary to dynamically "page" rows to the client browser as the user moves through the dataTable contents via the vertical scrollbar. Not only do rows need to be dynamically loaded or pre-loaded for the user, but rows must eventually also be dynamically removed from the browser DOM in order to prevent the eventual negative performance implications of an very large DOM in the browser, and the memory consumption that goes along with it.
Issue Links
- blocks
-
ICE-7476 DataTable: Live scrolling incompatible with lazy loading
- Closed
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion