|> > This makes absolutely no sense at all. If it's not readily
|> > available as a .HLP file, why should a .HTML version be more
|> > readily accessible?
|> Because some people do internet from their Unix accounts.
|> > People usually write Windows programs on their PC.
|> > If I want help, I will just click on an icon for
|> > the local .hlp file - I certainly wouldn't make a Web connection
|> > to do so.
|> Correct. But if you are trying to help someone and you don't have a PC
|> handy, what do you do?
|> > Besides, HTML, although slick & powerful would be
|> > a step backwards for accessing the API .HLP contents.
|> Not necessarily. It's quite easy, and actually becoming standard, to setup
|> a fulltext search on the collection using WAIS. And not all people have
|> Books Online.
|> Another advantage of WWW is that you have universal addressing of
|> topics. This is not a big deal when you're talking about one help file, but
|> if the initiative grows bigger, it will become important. You'll tell
|> someone "Read http://www.microsoft.com/BooksOnline/MFC/ODBC/Encyclopedia/
|> Snapshots.htm" instead of "RTFM about snapshots you lazy bum".
|> And of course, WWW is not just hypertext, WWW is distributed hypertext.
|> So, in the API topic about window styles, we can add "take a look at this
|> <a href="ftp://ftp.microsoft.com/softlib/mslfiles/STYLES.ZIP">sample</a>
|> from Microsoft"
|> Your reasoning above is somewhat similar to someone who says "Why did they
|> spend so much money to make OED and Webster electronic? It's much easier to
|> get my copy from the shelf". BTW what do you think of Project Gutenberg?
|> How about the Gutenberg press? ;-)
While all of these is true, I'd much prefer having a WWW FAQ (a real one,
that can tell the newbies how to term-wait, how to gray a ctrl...).
Freeman Installer==> ftp.arch.su.edu.au /pub/tongk/fi21_a.zip + fi21_b.zip
Key Center of Design Computing, Sydney University