unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gavin Smith <gavinsmith0123@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Per Bothner <per@bothner.com>,
	Texinfo <bug-texinfo@gnu.org>
Subject: Re: Any interest in using HTML for locally-installed Texinfo documentation?
Date: Tue, 9 Apr 2019 00:46:09 +0100	[thread overview]
Message-ID: <20190408234609.GA9976@darkstar.example.net> (raw)
In-Reply-To: <87k1g4v8dq.fsf@gnu.org>

On Mon, Apr 08, 2019 at 05:12:17PM +0200, Ludovic Courtès wrote:
> Neat!
> 
> From a “social” viewpoint, I think WebKitGTK would be more appropriate,
> GTK+/GNOME being affiliated with GNU.

It's the "social" viewpoint that will make it a success.  We don't just
need a proof-of-concept or something that is 95% complete, we need something 
that is reliable and complete, and that people will find easy to install 
and use, and also that we can continue to develop and maintain.

I'm still trying to implement very basic functionality in the Qt code.
I will probably push on with it and see how far I get.  If GTK is used 
instead, the needed functionality would be present, and the Qt code 
would be a prototype.

I expect it would be easier to integrate GTK-based code with an automake 
build system (Qt has its own build system tool, qmake).  I understand 
from reading various blogs and so forth that GTK has its own problems, 
too.  However, it is still plausible that it could be used.

> Also, QtWebEngine relies on bits of Chromium, which is a real challenge
> from a software freedom viewpoint and from a security viewpoint, to the
> point that we ended up removing it from our Qt builds in Guix:
> 
>   https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/qt.scm#n143
>   https://lists.gnu.org/archive/html/guix-devel/2015-06/msg00302.html

Those messages don't give a very promising picture.

I like the idea of a simple help browser with few dependencies, as it 
means you still be able to get some help even if more complicated/novel 
things are broken.

  parent reply	other threads:[~2019-04-08 23:43 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 12:55 Any interest in using HTML for locally-installed Texinfo documentation? Gavin Smith
2019-04-01 14:01 ` sirgazil
2019-04-02  9:37 ` Ludovic Courtès
2019-04-02 15:02   ` Gavin Smith
2019-04-02 16:46     ` Per Bothner
2019-04-07 16:28       ` Gavin Smith
2019-04-08 15:12         ` Ludovic Courtès
2019-04-08 15:39           ` Pierre Neidhardt
2019-04-08 23:46           ` Gavin Smith [this message]
2019-04-09  6:25             ` Eli Zaretskii
2019-04-13 16:21           ` Gavin Smith
2019-04-14 19:25             ` Pronaip
2019-10-15 19:27             ` Gavin Smith
2019-10-15 20:20               ` P
2019-10-15 20:35                 ` Gavin Smith
2019-10-15 20:40                 ` Per Bothner
2019-10-15 21:00                   ` Gavin Smith
2019-10-15 21:09                     ` Per Bothner
2019-10-15 21:30                       ` Gavin Smith
2019-10-16  1:39               ` Ricardo Wurmus
2019-10-19 20:31               ` Ludovic Courtès
2019-10-22 19:00                 ` Gavin Smith
2019-10-22 20:18                   ` Gavin Smith
2019-11-03 14:04                   ` Ludovic Courtès
2019-11-03 15:37                     ` Gavin Smith
2019-11-06 21:49                       ` Ludovic Courtès
2019-04-03 21:21     ` Ludovic Courtès
2019-04-04 10:33       ` Gavin Smith
2019-04-02 15:31   ` Per Bothner
2019-04-03 21:11     ` Ludovic Courtès
2019-04-03 22:44       ` Per Bothner
2019-04-04 10:23       ` Gavin Smith
2019-04-04 16:02         ` Ludovic Courtès
2019-04-02 20:12   ` Ricardo Wurmus
2019-04-02 20:27     ` Ricardo Wurmus
2019-04-02 22:58       ` sirgazil
2019-04-02 22:10     ` Per Bothner
2019-04-02 23:09       ` sirgazil
2019-04-03  8:43         ` Gavin Smith
2019-04-03 14:23           ` sirgazil
2019-04-03 14:40             ` Per Bothner
2019-04-03 14:49       ` Ricardo Wurmus
2019-04-02 21:02 ` George Clemmer
2019-04-07 11:08   ` Gavin Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190408234609.GA9976@darkstar.example.net \
    --to=gavinsmith0123@gmail.com \
    --cc=bug-texinfo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=per@bothner.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).