On 27/06/2019 21:02, Thiago Macieira wrote:
On Thursday, 27 June 2019 01:07:45 PDT Konrad Rosenbaum wrote:
Please also keep in mind that a fair number of developers use the same
tool-chain (qdoc, assistant, QtHelp) to generate their own documentation
- this means that assistant gets redistribute
A very good post, thank you Jarek.
Ideally, Qt would have a dedicated HTML renderer that works on all
platforms, without unnecessary overhead and security issues. Possibly as
a new widget (QHtmlBrowser) to keep QTextBrowser strictly rich text,
possibly removing features from QTextBrowser to ma
On 27/06/2019 06:57, Richard Weickelt wrote:
Qt used to make a point on having superior documentation to most other
frameworks, and it was (and still is) one of the reasons for its success.
Whatever we can do to help make the documentation better is something I
think we should do.
[...]
I stopp
On 25/06/2019 18:16, Thiago Macieira wrote:
On Tuesday, 25 June 2019 09:05:21 PDT Konstantin Tokarev wrote:
It hasn't been updated in years. Don't use it, since it's clearly not
getting security updates.
New version is currently in development, and should be ready in time frame
of Qt 5.14 (at l
On 26/06/2019 00:15, Jean-Michaël Celerier wrote:
There's also Zeal which is a nice Qt-based documentation browser which
covers much more than the current .qch offering: https://zealdocs.org/
& https://github.com/zealdocs/zeal
I see it used more and more.
Best,
Jean-Michaël
That's QWebView b
On 25/06/2019 21:30, Konrad Rosenbaum wrote:
It is documentation for developers for crying out loud!
No it is not. Assistant is distributed as a help viewer, to be
distributed along with applications for use by the customers of your
customers. As soon as QTextBrowser in its current sorry st
On 21/06/2019 11:08, Bastiaan Veelo wrote:
[...] The best solution would therefore be, in my opinion, to change
the order of compilation, apply the existing patch, and consider
refactorings and unifications thereafter.
I went ahead and did this. https://github.com/veelo/qttools is a fork of
On 21/05/2019 14:50, Konstantin Tokarev wrote:
21.05.2019, 15:47, "Bastiaan Veelo" :
On 20/05/2019 19:02, Konstantin Tokarev wrote:
[...] Current version of QtWebKit from 5.212 works on Windows,
there are binaries at
http://download.qt.io/snapshots/ci/qtwebkit/5.212/lates
On 24/06/2019 22:44, Lars Knoll wrote:
Another +1 from me. Let’s stop fighting this. We need something that
can properly display any HTML content (and maybe PDF and things as
well) that we throw at it.
Thank you.
Bastiaan.
___
Development mailing li
On 21/06/2019 15:47, Konstantin Tokarev wrote:
21.06.2019, 16:40, "Bastiaan Veelo" :
On 21/06/2019 14:57, Volker Hilsheimer wrote:
I’m not Jarek, but I recall that Eddy made a suggestion [1] which I
think has been prematurely dismissed or at least not been discussed
su
On 21/06/2019 14:57, Volker Hilsheimer wrote:
I’m not Jarek, but I recall that Eddy made a suggestion [1] which I
think has been prematurely dismissed or at least not been discussed
sufficiently, which is:
* move the Qt Assistant functionality for searching and qch support
into a locally exec
On 21/05/2019 12:24, Kai Köhne wrote:
-Original Message-
From: Development On Behalf Of
Subject: [Development] Assistant WebKit/WebEngine support
Hi,
I am prepared to do some work on Qt Assistant, and I'd like to know how that
will be received.
Cool, great you want to tackle this 😊
[skipping many interesting points, sorry]
On 21/05/2019 16:06, Shawn Rutledge wrote:
Anyway I think Assistant is one of those cases where I would prefer to
keep using QTextBrowser and fix it up a bit more to suit, rather than
switching to a real browser engine. Light weight is a real advantage.
On 20/05/2019 19:02, Konstantin Tokarev wrote:
20.05.2019, 19:58, "Bastiaan Veelo" :
On 20/05/2019 17:56, Konstantin Tokarev wrote:
20.05.2019, 18:27, "Bastiaan Veelo" :
On 20/05/2019 16:51, Konstantin Tokarev wrote:
Note that it should be possible to rebuild Q
On 21/05/2019 12:24, Kai Köhne wrote:
-Original Message-
From: Development On Behalf Of
Subject: [Development] Assistant WebKit/WebEngine support
Hi,
I am prepared to do some work on Qt Assistant, and I'd like to know how that
will be received.
Cool, great you want to tackle this 😊
On 20/05/2019 17:56, Konstantin Tokarev wrote:
20.05.2019, 18:27, "Bastiaan Veelo" :
On 20/05/2019 16:51, Konstantin Tokarev wrote:
Note that it should be possible to rebuild QtTools with QtWebKit support,
for example this configuration is supported in Gentoo out of the box.
I
On 20/05/2019 16:51, Konstantin Tokarev wrote:
20.05.2019, 16:02, "Bastiaan Veelo" :
[...]
Qt Assistant officially only renders content with QTextBrowser
currently, which is too limited for many of us[1]. There are still
traces of greater WebKit times, but that code remains un
hanks,
Bastiaan Veelo
[1] https://bugreports.qt.io/browse/QTBUG-55866
[2] https://forum.qt.io/topic/102816/webkit-status-2019
[3] https://codereview.qt-project.org/#/c/111559/
___
Development mailing list
Development@qt-project.org
https://lists.qt-projec
18 matches
Mail list logo
