Community
Participate
Working Groups
Eclipse 4.0 does not support Intro, Intro needs to be supported for Eclipse 4.1. A separate bug will track the work in the UA component. The intro support must be backward compatible with intro configurations created in Eclipse 3.x.
Bug 322440 has been created to track the UA work.
I've commented on the other defect about what the shape of these changes would be...
Changing milestone, at this point I expect to be able to host the existing Intro without change...
Pushed in >20111125. commit de3b05122fa80634221165f19a1cd3ae6401dffd This is a start...the normal startup and 'standby' handling is done but now all operations work correctly. Specifically the 'Go to Workbench' (which creates a trim control for the welcome) is broken.
It turns out that Intro's 'go to Workbench' code accesses the internal TrimManager class. For my money I'd prefer to just get rid of the code that makes the trim version of the Intro altogether and just have 'go to Workbench' set standby to true and close the Welcome view. I've just tried most of the other operations and everything else seems to be OK on first look except for a known issue involving maximizing a stack outside the perspective stack when there is more than one perspective open.
If I'm reading Comment 5 correctly the problem is in opening up the mini toolbar that is added to the trim when you press "Go to workbench". I would be 100% in support of removing that toolbar, I have never felt that it added much value and I don't think anyone would miss it.
Chris, thanks for the input. After talking with McQ we think that perhaps the right solution (for both 3.x and 4.x) would be to switch from creating the specialized trim to instead *minimize* the Welcome view. The logic is that the current behavior leaves the Welcome visible to the user (so they can restore it without having to 'know' to go to Help->Welcome. Minimizing the stack will have the same basic behavior...Welcome will still be open and in the trim. What do you think ?
For now I've hacked a 'fix' for this my providing a stub of ITrimManager, see bug 365625 for details... Pushed in >20111205. commit ae6a1ca03cd12e1b18924c02836c25fecc81eb0f
Aggregate move to M5. Retarget to a different milestone if you wish...
The current behavior is about as good as we can get for 4.2. I'll mark this as fixed, we can open new defects if any egregious defects are found...