[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-dev
Subject:    Re: [Wireshark-dev] Windows HTML Help
From:       Graham Bloice <graham.bloice () trihedral ! com>
Date:       2021-05-26 19:28:25
Message-ID: CALcKHKoPUJeGPRkTn+TYaZRhjHzuzZfrKEJbZ6D5mu4gX769XQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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 <bubbasnmp@gmail.com> wrote:

> 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 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>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@wireshark.org
> ?subject=unsubscribe
>


-- 
Graham Bloice

[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr">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.</div><div dir="ltr"><br></div><div>Not sure \
what&#39;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.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, \
26 May 2021 at 18:02, chuck c &lt;<a href="mailto:bubbasnmp@gmail.com" \
target="_blank">bubbasnmp@gmail.com</a>&gt; wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-size:small"><a \
href="https://www.wireshark.org/lists/wireshark-dev/200701/msg00396.html" \
target="_blank">https://www.wireshark.org/lists/wireshark-dev/200701/msg00396.html</a><br></div><div \
style="font-size:small"><br></div><div style="font-size:small">&quot;Pressing the \
help button will:</div>- 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 <a href="http://wireshark.org" \
target="_blank">wireshark.org</a> online page<span class="gmail_default" \
style="font-size:small">&quot;</span><div><span class="gmail_default" \
style="font-size:small"><br></span></div><div><span class="gmail_default" \
style="font-size:small">Clicking links in Windows HTML Help viewer is painful (and a \
little unnerving) with script errors.</span></div><div><span class="gmail_default" \
style="font-size:small"><br></span></div><div><span class="gmail_default" \
style="font-size:small">Is it time to sunset and have Windows help act like \
non-Windows platforms?</span></div><div><span class="gmail_default" \
style="font-size:small">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?</span></div><div><span class="gmail_default" \
style="font-size:small"><br></span></div><div><span class="gmail_default" \
style="font-size:small">chuckc</span></div><div><span class="gmail_default" \
style="font-size:small"><br></span></div></div> \
___________________________________________________________________________<br> Sent \
via:      Wireshark-dev mailing list &lt;<a href="mailto:wireshark-dev@wireshark.org" \
                target="_blank">wireshark-dev@wireshark.org</a>&gt;<br>
Archives:      <a href="https://www.wireshark.org/lists/wireshark-dev" \
rel="noreferrer" target="_blank">https://www.wireshark.org/lists/wireshark-dev</a><br>
                
Unsubscribe: <a href="https://www.wireshark.org/mailman/options/wireshark-dev" \
rel="noreferrer" target="_blank">https://www.wireshark.org/mailman/options/wireshark-dev</a><br>
                
                    mailto:<a href="mailto:wireshark-dev-request@wireshark.org" \
target="_blank">wireshark-dev-request@wireshark.org</a>?subject=unsubscribe<br> \
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div \
dir="ltr"><div>Graham Bloice</div></div></div></div>


[Attachment #6 (text/plain)]

___________________________________________________________________________
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-request@wireshark.org?subject=unsubscribe


[prev in list] [next in list] [prev in thread] [next in thread]