[prev in list] [next in list] [prev in thread] [next in thread]
List: wireshark-dev
Subject: Re: [Wireshark-dev] Windows HTML Help
From: chuck c <bubbasnmp () gmail ! com>
Date: 2021-05-27 1:43:43
Message-ID: CAF4O9rQvdo=-5a+9q4TgKq-PjS7QAYUc38nvd4cRti=urrznew () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Just like the racks of backup tapes that never get tested, I've just found
that the CHM files my dev system has been dutifully building are empty.
Once I get that resolved, I'll try upping the IE level in
https://gitlab.com/wireshark/wireshark/-/blob/master/docbook/custom_layer_chm.xsl
.
Another option is to change the href target:
<p>See <a class="ulink" href="
https://gitlab.com/wireshark/wireshark/-/wikis/VOIPProtocolFamily"
target="_blank">VOIPProtocolFamily</a> for an overview of the used VoIP
protocols.</p>
Changing target="_top" to target="_blank" opens the link in a default
browser window (or additional tab if already open).
Works great but not sure if it reopens
https://gitlab.com/wireshark/wireshark/-/issues/15860
On Wed, May 26, 2021 at 4:30 PM Gerald Combs <gerald@wireshark.org> 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 <bubbasnmp@gmail.com <mailto:
> bubbasnmp@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-request@wireshark.org <mailto:
> wireshark-dev-request@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-request@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-request@wireshark.org
> ?subject=unsubscribe
>
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_default" style="font-size:small">Just like the racks \
of backup tapes that never get tested, I've just found that the CHM files my dev \
system has been dutifully building are empty.</div><div class="gmail_default" \
style="font-size:small">Once I get that resolved, I'll try upping the IE level in \
<a href="https://gitlab.com/wireshark/wireshark/-/blob/master/docbook/custom_layer_chm \
.xsl">https://gitlab.com/wireshark/wireshark/-/blob/master/docbook/custom_layer_chm.xsl</a>.</div><div \
class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" \
style="font-size:small">Another option is to change the href target:</div><div \
class="gmail_default" style="font-size:small"><p>See <a \
class="ulink" href="<a \
href="https://gitlab.com/wireshark/wireshark/-/wikis/VOIPProtocolFamily">https://gitlab.com/wireshark/wireshark/-/wikis/VOIPProtocolFamily</a>" \
target="_blank">VOIPProtocolFamily</a> for an overview of the used \
VoIP protocols.</p><br></div><div class="gmail_default" \
style="font-size:small"><br></div><div class="gmail_default" \
style="font-size:small">Changing target="_top" to \
target="_blank" opens the link in a default browser window (or additional \
tab if already open).<br></div><div class="gmail_default" \
style="font-size:small">Works great but not sure if it reopens <a \
href="https://gitlab.com/wireshark/wireshark/-/issues/15860">https://gitlab.com/wireshark/wireshark/-/issues/15860</a></div><div \
class="gmail_default" style="font-size:small"><br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 26, 2021 at 4:30 PM \
Gerald Combs <<a href="mailto:gerald@wireshark.org">gerald@wireshark.org</a>> \
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">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.<br> <br>
<br>
On 5/26/21 12:28 PM, Graham Bloice wrote:<br>
> 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.<br> > <br>
> 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.<br> > <br>
> On Wed, 26 May 2021 at 18:02, chuck c <<a href="mailto:bubbasnmp@gmail.com" \
target="_blank">bubbasnmp@gmail.com</a> <mailto:<a \
href="mailto:bubbasnmp@gmail.com" target="_blank">bubbasnmp@gmail.com</a>>> \
wrote:<br> > <br>
> <a href="https://www.wireshark.org/lists/wireshark-dev/200701/msg00396.html" \
rel="noreferrer" target="_blank">https://www.wireshark.org/lists/wireshark-dev/200701/msg00396.html</a> \
<<a href="https://www.wireshark.org/lists/wireshark-dev/200701/msg00396.html" \
rel="noreferrer" target="_blank">https://www.wireshark.org/lists/wireshark-dev/200701/msg00396.html</a>><br>
> <br>
> "Pressing the help button will:<br>
> - 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" rel="noreferrer" \
target="_blank">wireshark.org</a> <<a href="http://wireshark.org" rel="noreferrer" \
target="_blank">http://wireshark.org</a>> online page"<br> > <br>
> Clicking links in Windows HTML Help viewer is painful (and a little \
unnerving) with script errors.<br> > <br>
> Is it time to sunset and have Windows help act like non-Windows \
platforms?<br> > 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?<br> > \
<br> > chuckc<br>
> <br>
> ___________________________________________________________________________<br>
> Sent via: Wireshark-dev mailing list <<a \
href="mailto:wireshark-dev@wireshark.org" \
target="_blank">wireshark-dev@wireshark.org</a> <mailto:<a \
href="mailto:wireshark-dev@wireshark.org" \
target="_blank">wireshark-dev@wireshark.org</a>>><br> > Archives: <a \
href="https://www.wireshark.org/lists/wireshark-dev" rel="noreferrer" \
target="_blank">https://www.wireshark.org/lists/wireshark-dev</a> <<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> \
<<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> <mailto:<a \
href="mailto:wireshark-dev-request@wireshark.org" \
target="_blank">wireshark-dev-request@wireshark.org</a>>?subject=unsubscribe<br> \
> <br> > <br>
> <br>
> -- <br>
> Graham Bloice<br>
> <br>
> ___________________________________________________________________________<br>
> Sent via: Wireshark-dev mailing list <<a \
href="mailto:wireshark-dev@wireshark.org" \
target="_blank">wireshark-dev@wireshark.org</a>><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> > \
<br> <br>
___________________________________________________________________________<br>
Sent via: Wireshark-dev mailing list <<a \
href="mailto:wireshark-dev@wireshark.org" \
target="_blank">wireshark-dev@wireshark.org</a>><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>
[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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic