Bugzilla – Full Text Bug Listing
| Summary: | [Intro] Adapt to changes made in platform UI intro support for Eclipse 3.7 and 4.1 | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Chris Goldthorpe <cgold> |
| Component: | User Assistance | Assignee: | platform-ua-inbox <platform-ua-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | prakash, remy.suen |
| Version: | 4.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | 322439 | ||
| Bug Blocks: | |||
|
Description
Chris Goldthorpe
Chris, I'm hoping that we can agree on a new approach for intro in 3.7 that would allow us to use the same code for both 3.x and 4.x. My current thoughts were to make the 'Intro' its own perspective. The magic would lie in having the perspective... 1) Not show up in the Perspective Switcher 2) Not be closable (opening is fine since it would just bring you back to what we currently get using Window->Welcome). 3) The perspective would be tagged (somehow) to indicate that the trim should be suppressed. If we do this the only difference from the user's pov would be that the initial 'Intro' wouldn't be in a 'maximized' stack, it'd just be a perspective with no editor area and just a single view. I think that the only changes we would have to make to the actual handling of the view is to remove the 'standby' logic (is it possible to change the style based on the view's area?) What are your thoughts? Does this sound like a reasonable approach? I'm wondering if we can really get rid of standby mode since public void standbyStateChanged(boolean standby) is in the API class org.eclipse.ui.intro.IIntroPart. org.eclipse.ui.intro.config.CustomizableIntroPart also has a notion of standby state which it uses for example after a tutorial is opened from the tutorials page. There are a number of things I don't like about the way intro works and the standby vs non standby mode is one of them but it is heavily ingrained in the existing code so it may take some work to move towards a new mode of operation and still have intro behave at least as well as before when you perform operations like opening a view when intro is showing, minimizing, maximizing and closing intro or opening a tutorial. What is it about Eclipse 4.0 which makes it incompatible with the 3.x intro? Deferred - Intro support did not make it into Eclipse 4.1 This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag. |