Qt Creator 4.11 comes with an optional
[[https://github.com/litehtml/litehtml][litehtml]] based help rendering
backend. To change the used
backend, go to Options > Help > General, and choose "litehtml" as the "Viewer
backend". All new help
viewers will use the changed backend, so e.g. after Qt
On 25/06/2019 17.53, Konrad Rosenbaum wrote:
> Option 2: put some elbow grease into QTextBrowser and make it understand
> some more tags and more CSS.
> Pros: documentation becomes visually more pleasing; minimal dependencies
> by assistant - easy to build and easy to bundle with applications;
> em
Catching up with mail discussions that have happened while I've been
away, so sorry if I've missed some relevant part that covers this
already ...
On 25. Jun 2019, at 23:53, Konrad Rosenbaum wrote:
>> Option 6: use plain platform browser to show local files
>> Pros: minimal footprint; assistant c
On Montag, 24. Juni 2019 11:32:15 CEST Konstantin Tokarev wrote:
> > Well, what I’d really like would be a lightweight RichText / HTML+CSS
> > viewer without all the baggage of a complete internet browser. QTextBrowser
> > does too little, QtWebEngine much too much.
>
> So, QtWebKit should be t
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 redistribu
From: Development on behalf of Palaraja,
Kavindra
Sent: Friday, June 28, 2019 10:56 AM
To: Qt development mailing list
Subject: Re: [Development] Assistant WebKit/WebEngine support
On 28.06.19, 10:24, "Eike Ziller" wrote:
> On 27. Ju
> On Jun 28, 2019, at 14:46, Palaraja, Kavindra wrote:
>
> On 28.06.19, 12:22, "Eike Ziller" wrote:
>
>
>
>> From your response, I'm only gathering two options:
>
>There are other options.
>https://lists.qt-project.org/pipermail/development/2019-June/036712.html
>summarizes
On 28.06.19, 12:22, "Eike Ziller" wrote:
> From your response, I'm only gathering two options:
There are other options.
https://lists.qt-project.org/pipermail/development/2019-June/036712.html
summarizes many of them.
Additionally “strip down QtWebEngine or QtWebKit and
> On Jun 28, 2019, at 10:56, Palaraja, Kavindra wrote:
>
> On 28.06.19, 10:24, "Eike Ziller" wrote:
>
>> On 27. Jun 2019, at 15:46, Palaraja, Kavindra wrote:
>>
>> On 27.06.19, 10:47, "Development on behalf of Jaroslaw Kobus"
>> wrote:
>>
>> QTextBrowser promises to render rich text - is
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
I will just chime in here to repeat one important point:
Chromium receives fixes for security problems every few weeks, at least. We
typically release new versions of Qt Creator much less frequently. We cannot
expose an unsafe web browser to our users, at least not without risking some
major f
On 27.06.19 20:14, Thiago Macieira wrote:
On Wednesday, 26 June 2019 18:47:32 PDT Lars Knoll wrote:
Yes, Webengine uses some memory. But is that really a problem on
developer
machines?
[...]
I'm not saying that Qt Web Engine would be a problem. I was arguing against
"memory is not a problem on
On 28.06.19, 10:24, "Eike Ziller" wrote:
> On 27. Jun 2019, at 15:46, Palaraja, Kavindra
wrote:
>
> On 27.06.19, 10:47, "Development on behalf of Jaroslaw Kobus"
wrote:
>
> QTextBrowser promises to render rich text - isn’t it what we want for
showing help? If QTextBrowser
> On Jun 28, 2019, at 10:24, Eike Ziller wrote:
>
>
>
>> On 27. Jun 2019, at 15:46, Palaraja, Kavindra wrote:
>>
>> On 27.06.19, 10:47, "Development on behalf of Jaroslaw Kobus"
>> wrote:
>>
>> QTextBrowser promises to render rich text - isn’t it what we want for
>> showing help? If QTe
> On 27. Jun 2019, at 15:46, Palaraja, Kavindra wrote:
>
> On 27.06.19, 10:47, "Development on behalf of Jaroslaw Kobus"
> wrote:
>
> QTextBrowser promises to render rich text - isn’t it what we want for showing
> help? If QTextBrowser isn’t able to render properly the static help files -
development@qt-project.org
Subject: Re: [Development] Assistant WebKit/WebEngine support
> On 28 Jun 2019, at 07:59, Martin Smith wrote:
>
>> That's what I'm trying to explain. I can't use what Creator gives me right
>> now
>> as it doesn't match what
___
> From: Development on behalf of Palaraja,
> Kavindra
> Sent: Friday, June 28, 2019 7:40 AM
> To: development@qt-project.org
> Subject: Re: [Development] Assistant WebKit/WebEngine support
>
> On 27.06.19, 20:59, "Development on
documentation site to get what it needs?
From: Development on behalf of Palaraja,
Kavindra
Sent: Friday, June 28, 2019 7:40 AM
To: development@qt-project.org
Subject: Re: [Development] Assistant WebKit/WebEngine support
On 27.06.19, 20:59, "Development on behalf of André Pönitz"
wrote
On 27.06.19, 20:59, "Development on behalf of André Pönitz"
wrote:
> People propose adding functionality to QTextBrowser instead. I do not
> thing that’s a viable solution (we’ve tried that in the past and our
> technical writers hit the next issue some weeks/months later). The
> On Jun 27, 2019, at 16:55, Simon Hausmann wrote:
>
>
> Am 26.06.19 um 14:44 schrieb Kirill Burtsev:
>> Hi,
>>
>> sorry, but that is not a right way to assess thing like memory consumption.
>>
>> Windows shows in a task manager just private memory (can not be used
>> by other processes) usa
27.06.2019, 22:15, "André Pönitz" :
> On Thu, Jun 27, 2019 at 06:57:08AM +0200, Richard Weickelt wrote:
>> Is it well known, how many QtCreator users are even using the integrated
>> help functionality? How many Qt users are using QtAssistant and how many
>> prefer the online documentation?
>
On Thu, Jun 27, 2019 at 06:57:08AM +0200, Richard Weickelt wrote:
> Is it well known, how many QtCreator users are even using the integrated
> help functionality? How many Qt users are using QtAssistant and how many
> prefer the online documentation?
The exact numbers are not known (to me), but th
On Thursday, 27 June 2019 01:07:45 PDT Konrad Rosenbaum wrote:
> Just to make sure I just installed Qt 5.13 for MinGW 7.3 on my Windows
> VM - WebEngine is nowhere to be seen. (Sorry, I don't have enough
> capacity to check whether I might be able to compile it myself using clang.)
You don't need
On Thu, Jun 27, 2019 at 01:47:32AM +, Lars Knoll wrote:
> Yes, Webengine uses some memory. But is that really a problem on
> developer machines?
On three out of four machines that I use with Qt Creator regularly
have limitations that make the presence of WebEngine undesirable.
These three mig
Hi,
On 6/27/19 3:47 AM, Lars Knoll wrote:
>
> Yes, Webengine uses some memory. But is that really a problem on developer
> machines?
It is a problem, but IMHO not the main problem. The main problem is that
WebEngine is not available on all platforms that are supported (as a
development host) by
On Thursday, 27 June 2019 07:39:29 PDT Lars Knoll wrote:
> > On 27 Jun 2019, at 08:25, Thiago Macieira
> > wrote:
> > On Wednesday, 26 June 2019 18:47:32 PDT Lars Knoll wrote:
> >> Yes, Webengine uses some memory. But is that really a problem on
> >> developer
> >> machines?
> >
> >
> > Yes. I h
Am 26.06.19 um 14:44 schrieb Kirill Burtsev:
> Hi,
>
> sorry, but that is not a right way to assess thing like memory consumption.
>
> Windows shows in a task manager just private memory (can not be used
> by other processes) usage for process. And that is really takes 15-20 Mb
> but just for sepa
> On 27 Jun 2019, at 08:25, Thiago Macieira wrote:
>
> On Wednesday, 26 June 2019 18:47:32 PDT Lars Knoll wrote:
>> Yes, Webengine uses some memory. But is that really a problem on developer
>> machines?
>
> Yes. I have 16 GB of RAM and 16 GB of swap. Sometimes Linux fails to suspend
> to disk
> On 27 Jun 2019, at 16:03, Alberto Mardegan
> wrote:
>
> On 27/06/19 14:14, Bastiaan Veelo wrote:
>>
>> However, it seems that most web browsers that implemented their own
>> browser tech have ditched those in favour of a third party framework
>> (see Opera, Edge, e.g.) -- how much of the reas
> On 27 Jun 2019, at 11:25, Bastiaan Veelo wrote:
>
> 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 doc
On 27/06/19 14:14, Bastiaan Veelo wrote:
>
> However, it seems that most web browsers that implemented their own
> browser tech have ditched those in favour of a third party framework
> (see Opera, Edge, e.g.) -- how much of the reason for that is due to
> rendering or networking I don't know.
I
On 27.06.19, 10:47, "Development on behalf of Jaroslaw Kobus"
wrote:
QTextBrowser promises to render rich text - isn’t it what we want for showing
help? If QTextBrowser isn’t able to render properly the static help files -
what is the other typical usage of it? Why we claim that QTextBrowser i
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 Tue, Jun 25, 2019 at 3:12 PM Giuseppe D'Angelo via Development
wrote:
> Are you referring to the 1px table wrapping the list of members, etc.?
>
> Saying that we want to move to a full blown browser for that makes me
> think that this is a case of Qt not eating its own dogfood. Is it
> impossib
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 Thu, 27 Jun 2019 08:47:07 +0300
Alberto Mardegan wrote:
> On 27/06/19 04:47, Lars Knoll wrote:
> >
> > Yes, Webengine uses some memory. But is that really a problem on developer
> > machines?
>
> Yes. The more RAM you use for surfing documentation, the less RAM you
> have for building. I ha
QTextBrowser promises to render rich text - isn’t it what we want for showing
help? If QTextBrowser isn’t able to render properly the static help files -
what is the other typical usage of it? Why we claim that QTextBrowser is able
to do things, which in fact it can't? This doesn't show a fair m
reasons for its success.
> Whatever we can do to help make the documentation better is something I think
> we should do.
>
> Cheers,
> Lars
>
>>
>> Br, Eike
>>
>>> That number came from the task manager in Windows.
>>>
>>> Simon
>&g
On Wednesday, 26 June 2019 18:47:32 PDT Lars Knoll wrote:
> Yes, Webengine uses some memory. But is that really a problem on developer
> machines?
Yes. I have 16 GB of RAM and 16 GB of swap. Sometimes Linux fails to suspend
to disk unless I quit either Creator, Firefox or Chromium. Free memory i
On 27/06/19 04:47, Lars Knoll wrote:
>
> Yes, Webengine uses some memory. But is that really a problem on developer
> machines?
Yes. The more RAM you use for surfing documentation, the less RAM you
have for building. I have 16 GB of RAM, and sometimes I have to close
Chromium away (yes, I know,
> 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.
Is it well known, how many QtCreator users are even
should do.
Cheers,
Lars
>
> Br, Eike
>
>> That number came from the task manager in Windows.
>>
>> Simon
>> From: Development on behalf of Michal
>> Klocek
>> Sent: Wednesday, June 26, 2019 13:31
>> To: development@qt-project.org
>
On Tue, Jun 25, 2019 at 08:58:07PM +, Tor Arne Vestbø wrote:
>
>
> > On 25 Jun 2019, at 22:53, André Pönitz wrote:
> >
> > On Tue, Jun 25, 2019 at 07:59:16PM +, Tor Arne Vestbø wrote:
> >>> On 25 Jun 2019, at 21:30, Konrad Rosenbaum wrote:
> >>>
> >>> Pardon my lingo,
> >>
> >> You s
M usage increase then.
Br, Eike
> That number came from the task manager in Windows.
>
> Simon
> From: Development on behalf of Michal
> Klocek
> Sent: Wednesday, June 26, 2019 13:31
> To: development@qt-project.org
> Subject: Re: [Development] Assistant WebKit/WebEngine
Yes, we never felt the styles should be exactly same, but the most suitable for
each purpose.
Leena
Date: Wed, 26 Jun 2019 11:39:18 +
From: Christian Kandeler
To: "development@qt-project.org"
Subject: Re: [Development] Assistant WebKit/WebEngine support
27;Detailed Memory Information' for every process.
Regard
From: Development on behalf of Simon
Hausmann
Sent: Wednesday, June 26, 2019 13:47
To: Michal Klocek; development@qt-project.org
Subject: Re: [Development] Assistant WebKit/WebEngine suppo
ndows.
Simon
From: Development on behalf of Michal
Klocek
Sent: Wednesday, June 26, 2019 13:31
To: development@qt-project.org
Subject: Re: [Development] Assistant WebKit/WebEngine support
Could you explain how did you measure web engine memory consumption to
get 14-20MB o
On Wed, 26 Jun 2019 11:24:30 +
Riitta-Leena Miettinen wrote:
> 3. Should the same style be used online and offline?
>
> For 3), we always answered „yes“, because we felt that the use cases for
> reading documentation on the web or using it within Qt Creator next to the
> Code editor were
Could you explain how did you measure web engine memory consumption to
get 14-20MB of ram ?
On 6/26/19 1:12 PM, Simon Hausmann wrote:
>
> Am 25.06.19 um 23:53 schrieb Konrad Rosenbaum:
>> Option 4: convert to WebEngine
>> Pros: looks great; currently supported browser engine, only little
>> port
araja, Kavindra"
To: "development@qt-project.org"
Subject: Re: [Development] Assistant WebKit/WebEngine support
Message-ID: <557ee263-e641-464f-b3b2-ac212c749...@luxoft.com>
Content-Type: text/plain; charset="utf-8"
Wow, I had no idea in my 12 years of being a Technical
Am 25.06.19 um 23:53 schrieb Konrad Rosenbaum:
> Option 4: convert to WebEngine
> Pros: looks great; currently supported browser engine, only little
> porting work
> Cons: horrible memory footprint; acute terminal featuritis; adds lots of
> dependencies (disqualifies it for most/many people redist
26.06.2019, 02:57, "Bastiaan Veelo" :
> 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
On 6/26/19 10:09 AM, Eike Ziller wrote:
>> On 25. Jun 2019, at 23:53, Konrad Rosenbaum wrote:
>>
>> Hi,
>>
>> On 6/25/19 9:59 PM, Tor Arne Vestbø wrote:
>>> On 25 Jun 2019, at 21:30, Konrad Rosenbaum wrote:
Pardon my lingo,
>>> You should be able to communicate your points without that kind
26.06.2019, 11:13, "Eike Ziller" :
> I agree with Thiago that this also requires WebKit to be updated with
> security fixes. It will potentially show downloaded content from anywhere,
> and it’s not nice if someone can offer a malicious qch, using known security
> issues in WebKit. And with Ja
I think the option 2 (enhancements in QTextBrowser) is the best one, since the
time investment spent on it will benefit for all users of QTextBrowser, not
only those using Qt help system. So big +1 here!
However, if we go with the webengine (or webkit) way, I would be very happy
that the existi
Hey Andre,
...
.. I find it somewhat strange that a party that
ships a custom Creator built anyway pushes so hard on a solution that
is harmful for some instead of simply building their help plugin in
their favourite configuration.
Andre'
Ah, yet another social stab instead
> On 25. Jun 2019, at 23:53, Konrad Rosenbaum wrote:
>
> Hi,
>
> On 6/25/19 9:59 PM, Tor Arne Vestbø wrote:
>> On 25 Jun 2019, at 21:30, Konrad Rosenbaum wrote:
>>> Pardon my lingo,
>> You should be able to communicate your points without that kind of lingo.
>> Try better.
>>
>>> It is docu
On Tuesday, 25 June 2019 18:08:28 PDT Thiago Macieira wrote:
> > Are you worried about the lack of security patches? I can see how that
> > matters for an ordinary browser implemented with Qt, but for Assistant
> > and Creator that exclusively display locally installed generated
> > compressed help
On Tuesday, 25 June 2019 17:07:20 PDT Bastiaan Veelo wrote:
> > at this point, what's speaking againt qtwebkit is its track record of
> > release. Until it starts making regular releases again, I can't recommend
> > it. And Qt Creator (or any other application) shouldn't begin using it
> > again un
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
> Feel free to correct/critique my assessment and to add more options if
you see any. Otherwise: chose your poison.
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 se
Hi,
On 6/25/19 9:59 PM, Tor Arne Vestbø wrote:
> On 25 Jun 2019, at 21:30, Konrad Rosenbaum wrote:
>> Pardon my lingo,
> You should be able to communicate your points without that kind of lingo. Try
> better.
>
>> It is documentation for developers for crying out loud! Its purpose is not
>> to
Il 25/06/19 16:30, Palaraja, Kavindra ha scritto:
The idea is to have parity in the sense of 1:1 appearance of how the
documentation looks like.
Here's a ticket that hasn't gone very far:
https://bugreports.qt.io/browse/QTCREATORBUG-15887
Can we keep the personal attacks out of this and perha
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 25 Jun 2019, at 22:53, André Pönitz wrote:
>
> On Tue, Jun 25, 2019 at 07:59:16PM +, Tor Arne Vestbø wrote:
>>> On 25 Jun 2019, at 21:30, Konrad Rosenbaum wrote:
>>>
>>> Pardon my lingo,
>>
>> You should be able to communicate your points without that kind of lingo. Try
>> better.
>
On Tue, Jun 25, 2019 at 07:59:16PM +, Tor Arne Vestbø wrote:
> > On 25 Jun 2019, at 21:30, Konrad Rosenbaum wrote:
> >
> > Pardon my lingo,
>
> You should be able to communicate your points without that kind of lingo. Try
> better.
>
> > It is documentation for developers for crying out lou
> On 25 Jun 2019, at 21:30, Konrad Rosenbaum wrote:
>
> Pardon my lingo,
You should be able to communicate your points without that kind of lingo. Try
better.
> It is documentation for developers for crying out loud! Its purpose is not to
> win any design prices, but to educate the develope
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
q
25.06.2019, 22:32, "Bastiaan Veelo" :
> 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
ht
Hi,
...my 2 cents or so...
On 6/25/19 4:30 PM, Palaraja, Kavindra wrote:
> No, parity isn't Google's search box. There's already a search feature in
> Creator.
>
> No, not "The Qt Company is hiring" either.
>
> The idea is to have parity in the sense of 1:1 appearance of how the
> documentation
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/latest/qtwebkit/
Ext
On Tue, Jun 25, 2019 at 10:52:29AM +0300, Konstantin Tokarev wrote:
> > It worked up to a certain degree nicely in the build system by
> > de-selecting options, than quite a bit more by actually removing code.
> > Getting rid of all of JS was not obviously possible.
>
> Removing code makes result
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 least functionality required for d
25.06.2019, 19:01, "Thiago Macieira" :
> On Tuesday, 25 June 2019 06:43:06 PDT Eike Ziller wrote:
>> What is the state of QtWebKit(2)
>
> 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 read
On Tuesday, 25 June 2019 06:43:06 PDT Eike Ziller wrote:
> What is the state of QtWebKit(2)
It hasn't been updated in years. Don't use it, since it's clearly not getting
security updates.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
No, parity isn't Google's search box. There's already a search feature in
Creator.
No, not "The Qt Company is hiring" either.
The idea is to have parity in the sense of 1:1 appearance of how the
documentation looks like.
Here's a ticket that hasn't gone very far:
https://bugreports.qt.io/brow
Am 25.06.2019 um 16:11 hat Giuseppe D'Angelo via Development geschrieben:
Saying that we want to move to a full blown browser for that makes me
think that this is a case of Qt not eating its own dogfood. Is it
impossible to fix QTextDocument to support them properly?
https://codereview.qt-proje
Hi,
Il 25/06/19 14:28, Palaraja, Kavindra ha scritto:
Hi Kirill,
I can’t speak for the size of WebEngine or the complexity of this
solution, but I can speak for the look & feel of the documentation.
The current situation with Qt Creator’s documentation is not about how
wonderful the conten
> On Jun 24, 2019, at 22:44, Lars Knoll wrote:
>
>
>> On 24 Jun 2019, at 21:54, Tor Arne Vestbø wrote:
>>
>>
>>
>>> On 24 Jun 2019, at 14:43, Simon Hausmann wrote:
>>>
>>> I have two more numbers to add: Compressed (7z) the download size would
>>> be around ~44 MB. I measured on Windows
> On Jun 25, 2019, at 10:26, Simon Hausmann wrote:
>
>
> Am 25.06.19 um 10:10 schrieb Morten Sørvig:
>> I’m not sure if it has been mentioned; we have another option which is to
>> use the OS web browser component via the Qt WebView module.
>>
>> The benefits would be
>>
>> * up-to-date web
…
I don't think that a lot of developers really care about how wonderful help
module looks like as long as it answers development related questions clearly
and precisely. Nowadays help/doc search activities is much more than just open
offline page with descriptions of classes and methods with e
ge misdirection.
From: Development on behalf of Simon
Hausmann
Sent: Monday, June 24, 2019 14:43
To: development@qt-project.org
Subject: Re: [Development] Assistant WebKit/WebEngine support
Am 24.06.19 um 12:31 schrieb Eike Ziller:
>> * What exactly is so big about WebEngine? What i
Am 25.06.19 um 10:10 schrieb Morten Sørvig:
> I’m not sure if it has been mentioned; we have another option which is to use
> the OS web browser component via the Qt WebView module.
>
> The benefits would be
>
> * up-to-date web browser (and someone else keeps it up to date for us)
> * insignific
Il 25/06/19 10:12, Simon Hausmann ha scritto:
I think you're right, the linkage appears to be due to the use of
QQuickWidget as child widget of QWebEngineView. Do you think that's a
problem?
I don't really know :)
I was asking about feedback regarding reintroducing a mandatory Qt Quick
depen
development@qt-project.org
Subject: Re: [Development] Assistant WebKit/WebEngine support
Hi,
Il 25/06/19 09:26, Simon Hausmann ha scritto:
>
> QtQuick 2 is not required for using WebEngine and there is support for
> software rendering. The existing Qt Creator integration as well as the
> pro
> On 24 Jun 2019, at 22:44, Lars Knoll wrote:
>
>
>> On 24 Jun 2019, at 21:54, Tor Arne Vestbø wrote:
>>
>>
>>
>>> On 24 Jun 2019, at 14:43, Simon Hausmann wrote:
>>>
>>> I have two more numbers to add: Compressed (7z) the download size would
>>> be around ~44 MB. I measured on Windows w
Hi,
Il 25/06/19 09:26, Simon Hausmann ha scritto:
QtQuick 2 is not required for using WebEngine and there is support for
software rendering. The existing Qt Creator integration as well as the
proposed patch to Qt Assistant to use Web Engine is using the widgets
integration.
To put it to a
25.06.2019, 10:48, "André Pönitz" :
> On Mon, Jun 24, 2019 at 04:37:16PM +0300, Konstantin Tokarev wrote:
>> > I have two more numbers to add: Compressed (7z) the download size would
>> > be around ~44 MB. I measured on Windows with a Qt Creator built with
>> > WebEngine support and surfed a l
nd
Chrome are all built using clang these days)
Simon
From: Development on behalf of Konrad
Rosenbaum
Sent: Tuesday, June 25, 2019 7:50
To: development@qt-project.org
Subject: Re: [Development] Assistant WebKit/WebEngine support
Hi,
On 6/24/19 2:43 PM, Simo
Giuseppe
D'Angelo via Development
Sent: Monday, June 24, 2019 15:52
To: development@qt-project.org
Subject: Re: [Development] Assistant WebKit/WebEngine support
Here's a third question:
On 24/06/2019 11:42, Palaraja, Kavindra wrote:
> Two further questions:
>
> * What exac
Hi,
On 6/24/19 2:43 PM, Simon Hausmann wrote:
> We've had this situation for a long time now and I think that we should
> finally move forward and give our users better quality at the expense of
> their disk space, memory consumption and download size.
...at the risk of making enemies: so the pl
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 Mon, Jun 24, 2019 at 01:49:12PM +, Palaraja, Kavindra wrote:
> +1, because:
>
> * It's 2019, we need to change with the times as documentation, especially
> how content looks and feels, has come really far from those days.
> * Almost 1:1 appearance of documentation in Creator vs. Browser.
> On 24 Jun 2019, at 21:54, Tor Arne Vestbø wrote:
>
>
>
>> On 24 Jun 2019, at 14:43, Simon Hausmann wrote:
>>
>> I have two more numbers to add: Compressed (7z) the download size would
>> be around ~44 MB. I measured on Windows with a Qt Creator built with
>> WebEngine support and surfed
On Mon, Jun 24, 2019 at 04:37:16PM +0300, Konstantin Tokarev wrote:
> > I have two more numbers to add: Compressed (7z) the download size would
> > be around ~44 MB. I measured on Windows with a Qt Creator built with
> > WebEngine support and surfed a little through the docs. The memory
> > consump
definitely
many ways it can be improved, compared to the web version.
пн, 24 июн. 2019 г. в 16:49, Cristian Adam :
> > -Original Message-
> > From: Development On Behalf Of
> > Simon Hausmann
> > Sent: Monday, 24 June 2019 14:44
> > To: development@qt-project
Here's a third question:
On 24/06/2019 11:42, Palaraja, Kavindra wrote:
Two further questions:
* What exactly is so big about WebEngine? What is this size that many are
hinting at but won't provide the number?
* Doesn't WebEngine have a feature where you can completely lock it out of the
Inte
+1, because:
* It's 2019, we need to change with the times as documentation, especially how
content looks and feels, has come really far from those days.
* Almost 1:1 appearance of documentation in Creator vs. Browser.
* Nobody needs to patch QTextBrowser and fix CSS now
* We will get code snippe
> -Original Message-
> From: Development On Behalf Of
> Simon Hausmann
> Sent: Monday, 24 June 2019 14:44
> To: development@qt-project.org
> Subject: Re: [Development] Assistant WebKit/WebEngine support
>
>
>
> I don't quite share the opinion t
1 - 100 of 134 matches
Mail list logo
