Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.6DR#4
-
Fix Version/s: 1.6.1
-
Component/s: ICE-Components
-
Labels:None
-
Environment:ICEfaces
-
ICEsoft Forum Reference:
-
Support Case References:
Description
Tables with a row selector show a linear curve of performance to # rows.
When there are over 200 rows, the row selector mouse over effect becomes very delayed. I specifically mention this as that effect is purely java script; therefore making no server round trip. All the other components are equally affected; such as clicking a button to move to the next page; can take upwards of 3-5 seconds.
When there are over 200 rows, the row selector mouse over effect becomes very delayed. I specifically mention this as that effect is purely java script; therefore making no server round trip. All the other components are equally affected; such as clicking a button to move to the next page; can take upwards of 3-5 seconds.
We will need to look at the specific JavaScript algorithm for handling the mouse overs. In the case of drag and drop, we were able to make substantial improvements to the collision detection algorithm by including a level-of-detail strategy (initially checking for collision at a low level of detail). Likely a similar strategy can be employed here.