Bug 130083 - [package explorer] Restore Package Explorer view's expansion state
Summary: [package explorer] Restore Package Explorer view's expansion state
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 65896 163255 216442 222194 228905 351327 398049 547446 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-03-02 02:30 EST by Marc Lehmann CLA
Modified: 2019-05-30 10:32 EDT (History)
12 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Lehmann CLA 2006-03-02 02:30:06 EST
[Eclipse 3.2M5a]

I would like to see an option to restore the state of the Package Explorer (tree structure) from the last session. Currently all the Working Sets / Projects are collapsed when restarting Eclipse.

Especially when working with many Working sets / Projects and having set the Package Explorer to show the Working Sets makes it laborious to come back where I have left off.
Comment 1 Martin Aeschlimann CLA 2006-03-12 17:38:33 EST
We had this in realier versions (1.1) but had to remove it as considerable time was spend on startup to restore the view (in particular classpath resolving).
Startup time is important and we couldn't justify the extra startup time in that case.
Comment 2 Dani Megert CLA 2008-01-25 11:13:18 EST
*** Bug 216442 has been marked as a duplicate of this bug. ***
Comment 3 Martin Aeschlimann CLA 2008-03-11 11:33:44 EDT
*** Bug 222194 has been marked as a duplicate of this bug. ***
Comment 4 Martin Aeschlimann CLA 2008-05-07 04:33:48 EDT
*** Bug 228905 has been marked as a duplicate of this bug. ***
Comment 5 Markus Keller CLA 2011-07-06 10:20:10 EDT
I agree this is a pain. We should either fix it, or offer a preference for users who don't care about startup time but do care about a consistent experience.

E.g. Preferences > Java:
[] Restore Package Explorer expansion state on startup
Comment 6 Markus Keller CLA 2011-07-06 10:20:54 EDT
*** Bug 65896 has been marked as a duplicate of this bug. ***
Comment 7 Markus Keller CLA 2011-07-06 10:21:05 EDT
*** Bug 163255 has been marked as a duplicate of this bug. ***
Comment 8 Markus Keller CLA 2011-07-06 10:21:29 EDT
*** Bug 351327 has been marked as a duplicate of this bug. ***
Comment 9 Dani Megert CLA 2011-07-06 10:54:11 EDT
+1 to fix it. The current behavior violates UI guidelines (see http://wiki.eclipse.org/index.php/User_Interface_Guidelines#Persistence).

If we add a preference then it should be a general workbench preference as this also affects the Project Explorer and the Navigator (which currently restores the expansion state). But we should try without such a preference.

For safety we could add an internal JDT preference without UI, so that a product can disable restoring the expansion state.
Comment 10 Luciano Mising name CLA 2011-07-06 11:08:07 EDT
I guess Java is just as much of a plug-in as a Pydev(Python), isn't it?
PyDev does it automatically but I have no idea if they infringe any guideline.
Maybe they got it right.
I just don't understand why this should be a preference when even the inherent Debug Perspective has it as normal behavior.
Comment 11 Remy Suen CLA 2011-07-06 11:15:52 EDT
(In reply to comment #10)
> I just don't understand why this should be a preference when even the inherent
> Debug Perspective has it as normal behavior.

Views generally do not care about which perspective they are in. I restarted Eclipse with the 'Package Explorer' expanded in both the 'Java' and 'Debug' perspectives and neither scenario preserved the expansion state.
Comment 12 Luciano Mising name CLA 2011-07-06 11:55:52 EDT
You are right, my Debug Perspective is probably being set by PyDev.
Comment 13 Dani Megert CLA 2013-01-14 09:46:57 EST
*** Bug 398049 has been marked as a duplicate of this bug. ***
Comment 14 Dani Megert CLA 2019-05-30 10:30:57 EDT
*** Bug 547446 has been marked as a duplicate of this bug. ***