> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>
> On Sat, 26 Jun 1999 22:46:36 +0200 (MET DST), you wrote:
>
> >> Oh, and if we are talking about electronic formats, I'd
> like to cast my
> >> vote for the Visual SlickEdit API format. I use it's
> tagging feature to
> >> let me "jump" to the prototypes in the headers, having the
> docs accessible
> >> the same way would be fantastic.
> >
> > why not just plain HTML?
>
> Because I'd like to be able to "pop up" the docs for any given OS call
> with a key press from my editor.
You should be able to do that w/ HTML & the proper binding
from your editor. If the editor can snatch the whole word
that the cursor is in the middle of, it need only invoke
the HTML browser with "helppage.html#functionname" (as long
as all of the API functions have "name" tags set up in the
help page...)
Windows help can also jump to certain locations in the
help file, but I don't know if they can be integrated
into external editors.
Visual SlickEdit is only One Man's Editor, so I would
not support that as the "default" help format.
PDF is nice for printing if they want to keep including
it, but we really need an -online- form of documentation.
While WinHelp is nice for my (and many developer's) purposes,
it wouldn't help the Mac folk, so HTML seems to be the
most reasonable choice, being both cross-platform AND
indexable. (note: they -MUST- index the heck out of
it though!)
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
