4 ms·
All Windows Help files ultimately are are a loose wrapper around Trident's HTML rendering engine. So why not avoid the needless complexity and simply just open
by Someone1234 12y ago
All Windows Help files ultimately are are a loose wrapper around Trident's HTML rendering engine.
So why not avoid the needless complexity and simply just open up the default browser and point it at a file:// location on the hard drive which corresponds to the index page which then uses relative URLs (and relative images) to open up sub-pages? Essentially a web server-less help system.
Doing it this way has the following advantages:
- The entire help system remains "offline."
- You can however link to "online" articles/content/etc.
- You can host exactly the same help files using a web-server, and they will work perfectly (because they use relative URLs).
- You can give the user the option of the offline one shipped with the software, or one you host which is updated.
Windows' Help system has a bunch of downsides. Using a subset of HTML (i.e. stuff that works in IE7) has few to no downsides, and at this point there is a real expectation that an end user will have a web-browser installed.
In Visual Studio 2013, when I click "View Help" it just opens up a web-page. I cannot see why anyone would do anything else at this stage, offline help doesn't even really change that, I'd still use HTML and a browser.