The TV package specializes the standard Java HTMLEditorKit for use as
a text view on specially annotated Isolde help pages.  See more  
documentation in the other files.

Things to do:
- add a "back" button and other nice browser features
- reuse existing TV panes when they exist (as is done by tamot for task panes)
- reimplement the domain model editing facilities so we can call the DM editor
       on the appropriate DM entity (rather than getting a list of all the 
       entities)
- this solution doesn't allow spans of text to be both hyperlinks and domain
       entities.  If this needs to happen, we'll have to modify the simple
       link listener to support choosing one or the other, perhaps using the 
       right mouse button for DM editing, and the left for following hyperlinks.
- similarly, because this solution uses the HTML anchor to represent DM
       entities as well as hyperlinks, Netscape and other standard browsers
       will treat DM entities as hyperlinks (with bad URLs).  One solution to
       this may be to have a separate generate-final-html command to doesn't
       put in the DM entity anchors.
- turn this view into a fully functional alternative to 
       the standard Diane Task view.  
- We must preserve the names of all java objects starting from tamot, passing
       through the generator and ending in the html file that the text view
       reads.  To do this, Tamot must maintain a link between the name of a 
       DM entity (i.e., a String) and the java object itself.  This way, the 
       lisp generator can put the name of domain model entity in the html 
       output and the text viewer can call up the DM object corresponding to
       that name.
- I couldn't test whether canned text fields are being done properly, for some
       reason, tamot is not dumping the <note> documentation fields.  They will
       be somewhat tricky given that they don't have a separate tamot DM entity
       to themselves.

kvlinden, 22feb00