Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320602 - [Tree] Improve performance of keyboard-navigation in big trees
Summary: [Tree] Improve performance of keyboard-navigation in big trees
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.4 M1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 320597
  Show dependency tree
 
Reported: 2010-07-22 05:21 EDT by Tim Buschtoens CLA
Modified: 2010-07-30 12:26 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Buschtoens CLA 2010-07-22 05:21:36 EDT 
In a big Tree, keyboard navigation is noticeably slower at the bottom than at the top. This is due to the way "_findIndexByItem" works. We should find a way to optimize that function.
Comment 1 Tim Buschtoens CLA 2010-07-30 12:26:10 EDT 
Fixed in CVS HEAD by refactoring findIndexByItem and key-handling in general in Tree.js. Keyboard-navigation in IE6 is still kinda slow (especially when holding down a key), but i think that is mostly rendering and therefore another issue. Any further optimization in the internal model-navigation logic would require caching more data, e.g. the focusItem index.