Description Miguel Griffa 2005-09-09 12:30:48 EDT

Currently, the javadoc view resolves the javadoc for an element in only one way,
flexible, configurable, but one way. I belive it would be desirable to extract
the way in which a java element is 'converted' into javadoc. This would allow to
modify the plugin to provide javadoc from different http locations, for example, 

This idea came to my mind while considering how cool would be to have a plugin
that provides javadoc info for almost everything, smart way. This would imply
having many registered javadoc sources in different places. While the actual
javadoc view could be a base source for such a plugin, providing extensibility
to current javadoc view would be greater. 

Some more refinement on how different sources of javadoc ar treated would also
be a point to consider, probably the user would be able to choose the order of
the javadoc sources, so when an element is to be resolved, the javadoc sources
are visited in the order the user defined.

Taking this a step further, tabs could be added to present the contents of the
different sources