I've been thinking about Jeff's statement about updating the docs
lately and would like to propose a possible fix. I'd like to hear
responses from everybody on my proposed solution.
It is possible to launch a browser from another application with a
given URL. Right now, we have the documentation available as html and
also the specially programmed internal docs. What if we were to add a
hook that made it possible to change the context sensitive help to
launch a browser onto the correct page. Wouldn't this be the most
excellent (as Bill and Ted would say) fix. I think the next step
beyond this would be to also include a Java applet that can search
the html documentation. We leave the internal help viewer in there
but if a browser can be located then it uses the html docs. How many
people don't have a browser on their system? Thus as we change the
documentation we only need to change the html docs.
The down sides to this that I see are that a browser does use more
resources (more memory) than just the help docs and the old help docs
become stagnant. But I don't see a way to update them at this time.
Please chime in--if everyone's in agreement that this is a good
thing, I might start working on it.
David
Definately my concern too. Thats why it would be necessary to edit the
documentation and context senstive help to explain the radius=0 option and
what it does and does not do.
Jeff
--
.............................................................................
David L. Thompson The University of Montana
mailto:[EMAIL PROTECTED] Computer Science Department
http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
Work Phone : (406)257-8530
