[ jEdit-devel ] ViewJavaDoc, ProjectViewer and JIndex

[Dirk M. <dmo...@gm...>]

I did some thinking about how these three could cooperate.

For a start, I assume that ViewJavaDoc will be integrated into
ProjectViewer, so that you can generate API doc on the whole project.

In ProjectViewer, you should have the ability to make a "final
release", for which a library name (a JAR/ZIP file) and a target
directory must be entered. If the user chooses to make a final release,
then ProjectViewer creates this lib and send a message to JIndex to
recreate the index for this lib. JIndex looks into its directory, if
this lib is already there and add it if necessary. So, JIndex only
recreates it's index, if the user makes a final release, because it's
a time consuming process.

ProjectViewer should also maintain a directory for the api doc
location, and send the location to JIndex on API doc creation time.
ProjectViewer locations override JIndex locations.

So the overall idea is that API doc locations are maintained via
ProjectViewer, and JIndex is only a repository for these, containing
ALL project APIs. When everything is round and running, one should'n
even need to edit anything on JIndex's Option pane (except for the base
libs: classes.zip and swing.jar).

I omitted a lot of details here, but this should give you a rough idea.
What do you think?

--
Dirk Moebius <dmo...@gm...>