Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 71214

Summary: [Intro] Get the user's attention after installing new feature (like old welcome did)
Product: [Eclipse Project] Platform Reporter: Leif Frenzel <himself>
Component: User AssistanceAssignee: platform-ua-inbox <platform-ua-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3 CC: dmichonneau
Version: 3.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description Leif Frenzel CLA 2004-08-02 03:32:11 EDT
The new Intro facilities lack a very helpful feature, used by third-party
contributions) that the old Welcome (Eclipse 2.1) had:

With the old welcome pages, you had a good chance to get the user's
attention after a new feature was installed. A common situation is when a
user has just installed a new feature about which he does know what it does
(roughly), but not where to start. For instance, the thing to do first is to
open a specific perspective that has been contributed by the feature, or it
may be triggering a certain popup menu item on a certain resource type, or
running a specific NewWizard, etc.

In the old story, the user would see the welcome page explaining this to
him. In the new model, he gets no message at all, or at best (but this
requires already a bit of guessing from a new user) the Intro. Even if the
new feature does add Intro items (or Help extensions), the user is, at the
start, several mouseclicks away from those, and here we already assume that
he knows his way around.

A possible solution could be one dedicated page of the Platform intro, which is
shown to the user every time she has installed something new (there could be a
preference to disable this behaviour). Newly installed features could then
contribute to such a page.
Comment 1 Chris Goldthorpe CLA 2007-04-04 15:58:48 EDT
We now show intro content when new feature with intro contributions are installed, see Bug 177635.

*** This bug has been marked as a duplicate of bug 177635 ***