Some comments on navigation and hovers

[aclement]

Some issues and some observations:

• showing content assist should hide the tooltip, annoying when they are both on screen.
• textview.js:1065 can't navigate to _init (can we really not tell where it is?)
• textview.js:1314, hover on getActions, lots of whitespace??
• scriptedEditor.js:278 - codeBindings. Put it in the middle of the screen (ctrl+l) now navigate to it, the line stays at 278 but it is moved to the top of the screen - should we really reposition the editor in this case? (when the user is already on the first occurrence)
• Can't recreate right now but for a period it was happening all the time. scriptedEditor.js:300 attempt to navigate to 'editor' took me into the jquery.min file.

Observations:

a) contentAssist.js:386. Hover on ContentAssistMode. Need some color on those @ elements or they need pulling out. Are they not being pulled out for separate formatting due to incorrect jsdoc format?

b) for some simple hover it looks a bit odd, to me, to have them on separate lines. e.g. layoutmanager.js:20, hover on getBoolean, there are two lines in the hover text, when one would suffice. Wonder if we should compress it onto one.

c) the trailing '}' aren't on a newline which I know is a little bit of a waste of space but makes the formatting look crude. E.g. scriptedEditor.js:101 hover over editor. Final '}' in the hover should be on a newline for the formatting to look right, this problem occurs everywhere.

d) scriptedEditor.js:161, hover on shouldExclude. parameter signature is split across lines, looks poor.

e) contentAssist.js:403, hover on cancel. Not sure the comment should be shown or it should be on all those members (as they are all getting the contribution)

f) a la Eclipse, when content assist is open the tooltip for the function should be shown in a box to the right of the content assist box if we have the information.

[aeisenberg]

Lots of things here. Some easy to fix, some hard.

I'll start by taking a look at the non-navigable links you have above and see if there are any improvements we can make.

As for formatting of hovers, particularly jsdoc, my intention is to use doctrine to parse the docs and then use that to feed into a formatter. However currently, doctrine is not error tolerant enough and will barf on too many reasonably formatted jsdoc comments.

[aeisenberg]

More work done in recent commit. Closing this issue. Raised issue #226 for remaining work.