A long-range goal could be to make capitalized
tokens into hypertext links to other source files (or
perhaps doc comment files for the library classes).
Resolving the appropriate source file for a token
could be done whenever the user modifies that token.
If the source file can't be resolved, the token could
be colored differently.
Because this strategy works without contextual
analysis (well, except for keeping track of the
import and package statements), it should be easy to
use it for the various tabbed panes. Hypertext links
would be especially useful with the compiler and
testing errors.
We could even include "back" and "forward" buttons in
the toolbar, but I don't want to get too far ahead of
things yet.
Story: The user clicks on a capitalized token
referring to a resolvable class. The corresponding
source file (or the hypertext doc comment file for a
library class) is brought into the definitions pane.
The user clicks on a link in the newly opened
document to bring that file into the definitions pane.
The user then modifies a capitalized token so that it
no longer refers to a valid class. The token is
immediately colored differently, to alert the user.
The user tries to click on the modified token, but
nothing happens.
-- Eric