Bug 149000 - [CommonNavigator] Selection and expansion state should be persisted between sessions
Summary: [CommonNavigator] Selection and expansion state should be persisted between s...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement with 3 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
: 250352 295942 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-06-28 10:13 EDT by Anton Leherbauer CLA
Modified: 2012-08-13 15:57 EDT (History)
5 users (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 Anton Leherbauer CLA 2006-06-28 10:13:04 EDT 
The selection and the expansion state of a Common Navigator (eg. Project Explorer) is not persisted. This should be handled by the Common Navigator framework itself (maybe as an option). This must be framework feature because content providers cannot restore the global selection and expansion state on their own without knowledge about other content extensions. They would eventually get in conflict with one another.
Comment 1 Michael D. Elder CLA 2006-07-11 09:35:43 EDT 
In general, this practice is no longer practiced (e.g. Package Explorer) because of the extra performance impact of restoring the state. In the case of the Common Navigator Framework, the problem is potentially very bad because of the amount of content that can be displayed -- and the number of plugins that could be required to load to restore the state. 

I'm deferring this to 3.3 for now, but it's likely that a fix will only be provided if there is enough community support for it.
Comment 2 Francis Upton IV CLA 2008-10-22 02:55:25 EDT 
*** Bug 250352 has been marked as a duplicate of this bug. ***
Comment 3 Francis Upton IV CLA 2009-11-23 18:13:06 EST 
*** Bug 295942 has been marked as a duplicate of this bug. ***
Comment 4 Mekk Elek CLA 2012-08-12 16:13:50 EDT 
Performance issues? Why not making it optional then and let users decide if they are willing to pay the price?