On Sun, Nov 03, 2019 at 03:04:27PM +0100, Ludovic Courtès wrote:
> > The work is available on the webkitgit-info branch of the texinfo git
> > repository. I think it is developed to a point where it shows that a
> > browser for locally installed HTML documentation is clearly possible
> > with
On Tue, Oct 22, 2019 at 8:00 PM Gavin Smith wrote:
> I tried to upload a demo video to
> https://goblinrefuge.com/mediagoblin/u/gavin/ but it hasn't appeared
> yet.
That doesn't seem to be working, so I've uploaded the video to
https://www.gnu.org/software/texinfo/video/demo.webm.
On Sat, Oct 19, 2019 at 9:31 PM Ludovic Courtès wrote:
> > I started another line of development, using the WebKitGTK engine.
> > http://git.savannah.gnu.org/cgit/texinfo.git/log/?h=webkitgtk-info
>
> [...]
>
> > I may be able to get an initial prototype that other people could try
> > ready in a
On Tue, Oct 15, 2019 at 02:09:59PM -0700, Per Bothner wrote:
> On 10/15/19 2:00 PM, Gavin Smith wrote:
>
> > JavaScript should not be necessary if there is DOM access from the C/C++
> > side, as the case with WebKitGTK (although it is not as easy as it could
>
On Tue, Oct 15, 2019 at 01:40:17PM -0700, Per Bothner wrote:
> On 10/15/19 1:20 PM, P wrote:
> > ‐‐‐ Original Message ‐‐‐
> > On Tuesday, October 15, 2019 7:27 PM, Gavin Smith
> > wrote:
> > > WebKitGTK seemed to be the best option for a lightweight embedd
On Tue, Oct 15, 2019 at 08:20:14PM +, P wrote:
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, October 15, 2019 7:27 PM, Gavin Smith
> wrote:
> > WebKitGTK seemed to be the best option for a lightweight embedded
> > web-browser. I looked into other options, such as the
Link to thread archive:
https://lists.gnu.org/archive/html/bug-texinfo/2019-04/msg1.html
On Sat, Apr 13, 2019 at 5:18 PM Gavin Smith wrote:
> I've moved forward enough with Qt and QtWebEngine that I'm confident
> that it could be used for all the required features: path search for
>
On Mon, Apr 08, 2019 at 05:12:17PM +0200, Ludovic Courtès wrote:
> > I've started work on a documentation browser using QtWebEngine. The
> > work can be seen in the qt-info branch of the Texinfo Git repository:
> >
> > http://git.savannah.gnu.org/cgit/texinfo.git/tree/js/docbrowser?h=qt-info
>
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
On Tue, Apr 02, 2019 at 05:02:19PM -0400, George Clemmer wrote:
> Gavin Smith writes:
> [...]
> > A manual with this interface added is at
> > https://www.gnu.org/software/texinfo/manual/texinfo-html/Overview.html.
> > All the important keyboard commands that
On Tue, Apr 02, 2019 at 09:46:05AM -0700, Per Bothner wrote:
> Both Electron and QtWebEngine have mechanisms for communicating between
> the "browser" window and the main application, which is not sandboxed.
> (For QtWebEngine the main application is regular non-sandboxed C++ code.)
> For a
On Wed, Apr 03, 2019 at 11:21:32PM +0200, Ludovic Courtès wrote:
> > One thought is that there may be other "layout engines" that could be
> > used, such as those in various GUI toolkits.
>
> Yes, the GTK+ stacks has everything we need to display hypertext
> content nicely, I believe.
OK, so
On Wed, Apr 03, 2019 at 11:11:36PM +0200, Ludovic Courtès wrote:
> I find things like DOMTerm very impressive, and it’s true that
> HTML/JS/CSS nowadays constitute an unequaled UI framework (to the point
> that GNOME Shell is also written in JS + CSS.)
>
> That would be a good argument in favor
On Tue, Apr 02, 2019 at 06:09:40PM -0500, sirgazil wrote:
> El 2/04/19 a las 5:10 p. m., Per Bothner escribió:
> >On 4/2/19 1:12 PM, Ricardo Wurmus wrote:
> >>As far as I know GNOME’s Yelp is a frontend to different kinds of
> >>documentation and it does support Info files.
> >
> >That reads
On Tue, Apr 02, 2019 at 11:37:51AM +0200, Ludovic Courtès wrote:
> (For some reason ‘i’ does open the index search box for me, but then
> hitting enter doesn’t produce any effect. The other navigation commands
> work fine, though.)
It works on Firefox 53, at least.
> Yet I’m not completely sold
Dear Guix developers,
I hope I am not intruding by advertising a project that may be of
interest to you.
Documentation for GNU packages and others is often installed in the
Info format, a plain text format. Using a plaintext based format for
documentation does not take advantage of bitmapped
16 matches
Mail list logo
