Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 70300 - Make shift-F2 work on SDK types
Summary: Make shift-F2 work on SDK types
Status: RESOLVED DUPLICATE of bug 52894
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-18 11:45 EDT by Ed Burnette CLA
Modified: 2004-07-19 09:58 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Burnette CLA 2004-07-18 11:45:34 EDT
When you hover over an SDK type like IPlatformRunnable you get its Javadoc in 
a little popup window. When you press F2 you get a bigger popup window. 
There's also a Javadoc view. All these are source-based. When you press Shift-
F2 (external Javadoc) you get an error message that says "The documentation 
location for 'IPlatform Runnable' has not been configured. For elements from 
libraries specify the Javadoc location URL on the properties page of the 
parent JAR ('runtime.jar')." If it matters I have done a binary import of all 
plug-ins.

If this were a Java JDK type and I was using a JDK instead of a JRE then this 
would have worked. It's just a problem for the Eclipse platform classes and 
types.

I shouldn't have to configure anything else to go to the Javadoc page for this 
type. I can navigate manually to the Javadoc page in the help but it's time 
consuming. The reason that hover and F2 are insufficient is that you don't get 
the context - you can't hyperlink to related types and packages. So the 
enhancement request is to automatically configure the settings so that shift-
F2 in the Java text editor will work on all Platform SDK types with no 
searching or special configuration needed on the user's part.

Not sure if the right product/component for this so please redirect as 
appropriate.
Comment 1 Dani Megert CLA 2004-07-19 05:59:34 EDT
Importing using PDE attaches the source and it could also fill in the correct
Javadoc path.
Comment 2 Ed Burnette CLA 2004-07-19 09:43:44 EDT
That would be ok though it would be even nicer if it didn't require an import 
step. If you're using an SDK symbol in your plug-in code then IIRC hover and 
F2 will work whether or not you've imported.
Comment 3 Wassim Melhem CLA 2004-07-19 09:58:13 EDT

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