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.
Actually, I guess in an ideal world we'd have this stuff in many formats,
because everyone's need's are slightly different. Not to mention that
fact that depending on what we are doing (learning or reviewing, we want
to be able to thumb through the docs, coding or debugging we want instant
info on a specific function, etc.)
* HTML - Good for browsing on-screen (see Java).
* Visual SlickEdit API - Pop-up info from the editor I use, YMMV!
* Other Editor formats - Because not everyone has discovered Visual
SlickEdit yet. ;-)
* Windows Help - Ubiquitous.
* PDF - Allows printing a nice hardcopy.
* Books - Best for browsing. Just something about a book...
Don Meyer
Stormgate Communications
