This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 225730 - Alt-F1 for JavaDoc access for Java Classes
Summary: Alt-F1 for JavaDoc access for Java Classes
Status: RESOLVED DUPLICATE of bug 194420
Alias: None
Product: groovy
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P2 normal (vote)
Assignee: Martin Janicek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-04 23:58 UTC by eddelplus
Modified: 2013-02-06 16:09 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description eddelplus 2013-02-04 23:58:00 UTC 
The editor seems to understand the groovy code well enough to recognize identifiers that are Java Classes already. Based on that, opening the corresponding Java Doc should also be possible via Alt-F1.
Comment 1 Martin Janicek 2013-02-05 13:10:19 UTC 
Hi eddelplus, probably not getting your point in this one :) ..what is the meaning of "identifiers that are Java Classes already"? Could you give me some steps that I should follow to see incorrect result?
Thanks in advance!
Comment 2 eddelplus 2013-02-05 23:11:02 UTC 
Hi Martin,

putting the cursor on BufferedWriter in "def out = new BufferedWriter" or in "import java.io.BufferedWriter" (though java.io is imported automatically) and pressing Alt-F1 should trigger Java Doc for that class. But nothing happens. For compiled classes on the class path there is no immediate distinction anyway whether they were created with Groovy or Java. But if it is a class in the core libraries or a class for which Java Doc has been scanned, that should be shown. 

Once the type inference bug gets tackled, there are probably more cursor locations where appropriate JavaDoc could be shown. The whole GroovyDoc and JavaDoc duality doesn't facility a consistent help experience. Even the Groovy web site itself had some problems joining the documentation based on Java Sources with the documentation based on Groovy Sources.

Cheers, Jochen
Comment 3 Martin Janicek 2013-02-06 16:09:08 UTC 
Thanks Jochen, I see your point now.. agree that this is something we should have. I'm going to take a look what needs to be implemented for such functionality (I believe this had never worked) and will evaluate later on.
Comment 4 Martin Janicek 2013-02-06 16:09:45 UTC 

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