I just discovered that the HTML Help Workshop download link at
https://docs.microsoft.com/en-us/previous-versions/windows/desktop/htmlhelp/microsoft-html-help-downloads
no longer works, and the Chocolatey package now downloads from archive.org:
https://community.chocolatey.org/packages/html-help-workshop#files
I'll take a look at switching the Windows installers over to plain HTML.
On 5/26/21 2:30 PM, Gerald Combs wrote:
I think the only advantage that HTML Help offers at this point is the ability
to search for keywords. It otherwise adds a build requirement which results in
shipping a different help format on Windows, and the HTML Help Viewer seems to
behave worse as time goes on. I'd be OK with switching to plain HTML.
On 5/26/21 12:28 PM, Graham Bloice wrote:
Personally I prefer help to be local and not require internet access, and I
despise those local help abominations that spew hundreds of html files into the
filesystem.
Not sure what's up with the links, maybe we need to make them pass off to the
system default browser rather than trying to render them in the HTML help
browser.
On Wed, 26 May 2021 at 18:02, chuck c <bubbas...@gmail.com
<mailto:bubbas...@gmail.com>> wrote:
https://www.wireshark.org/lists/wireshark-dev/200701/msg00396.html
<https://www.wireshark.org/lists/wireshark-dev/200701/msg00396.html>
"Pressing the help button will:
- on Win32 only: if available, open the Windows Help viewer with locally installed
user-guide.chm file - and if that fails ... - on all systems: start a web browser and open
the corresponding wireshark.org <http://wireshark.org> online page"
Clicking links in Windows HTML Help viewer is painful (and a little
unnerving) with script errors.
Is it time to sunset and have Windows help act like non-Windows platforms?
Or maybe add a step to the CHM build process that makes the links
non-clickable so the user would need to copy/paste into a browser?
chuckc
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org
<mailto:wireshark-dev@wireshark.org>>
Archives: https://www.wireshark.org/lists/wireshark-dev
<https://www.wireshark.org/lists/wireshark-dev>
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
<https://www.wireshark.org/mailman/options/wireshark-dev>
mailto:wireshark-dev-requ...@wireshark.org
<mailto:wireshark-dev-requ...@wireshark.org>?subject=unsubscribe
--
Graham Bloice
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
