Community
Participate
Working Groups
Currently in the source view, when hovering over an particular XML and a grammar is attached, information about the element is displayed. However, if in design view this annotation information isn't available, and it would be helpful to have it available as a separate view. This way, when the element is added or selected in the design editor, the annotation view would be updated with any annotation information that may exist in the grammar for that element.
Perhaps a request should be made to generalize the JavaDoc view into a "Documentation" view for such a purpose?
(In reply to comment #1) > Perhaps a request should be made to generalize the JavaDoc view into a > "Documentation" view for such a purpose? > Yes, if there is already an existing view that we could use as a base that would be good. I guess the platform would need to create the abstract view, and then let the various plugins, extend the view for their needs, like the outline view is done today. Maybe if I get some time, I'll take a crack at just creating a working view and use the javadoc view as a basis to start with (taking out any jdt specific dependencies). However, this may be a while before I get to doing this.
Another option would be to add another tab to the Properties view so that it could display the annotations.
(In reply to comment #3) > Another option would be to add another tab to the Properties view so that it > could display the annotations. It's an interesting idea, but views should only be about one thing.
Either way works for me, I prefer the separate view, to doing it with the properties view.
Agreed. It's an interesting idea but the core team for sure won't have time for it in 3.0. We'd happily accept high quality patches from someone motivated enough to work out the usability concerns, though. Whether that means advocating a "language documentation" view across the entire IDE is up to that contributor, assuming it's not the core team down the road.
Dave, would this be a proper use for a general purpose "Documentation" view like we discussed at EclipseCon?
(In reply to comment #7) > Dave, would this be a proper use for a general purpose "Documentation" view > like we discussed at EclipseCon? > Yes, a documentation view would be good. Based on the current node, grab any documentation and display it in the view. Another idea is to have a Content Model view that shows a tree view of the underlying content model, so that people can see what is easily insertable at a particular point in time.
