ambiguous documentation for SDK documentation path?
Answered
the main lines of explanation on this page are
You can add SDK documentation to IntelliJ IDEA so that you can get information about symbols and method signatures right from the editor in the Quick Documentation popup.
later in the example, it was shown how to attach a standard documentation source for JDK
but (e.g for jdk) you can see information about symbols and method signatures right from the editor in the Quick Documentation popup without adding any JDK documentation path|url,
if I am not missing something the only purpose of specifying the path for SDK (in my case JDK) documentation are
- specify another search place for symbols and method signatures different from the Javadoc of JDK
- get the opportunity to open documentation in the browser directly from IntelliJ IDEA
am I missing something?
Please sign in to leave a comment.
Apart from the mentioned reasons, there is also one more point:
External JDK documentation can have a bit more complete information when compared to the default javadoc provided by JDK automatically. You can try to compare documentation for
Doubleclass for example, with external JDK added and without.Anyway, you are right - the help page should mention that the documentation is already provided by default, but it could be expanded by adding external javadoc. We will report this to our technical writers team to see how it can be improved. Thank you!