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
> On 26 Jun 2019, at 23:16, Eike Ziller wrote:
>
>
>
>> On 26. Jun 2019, at 13:47, Simon Hausmann wrote:
>>
>> Hi,
>>
>> From my earlier email:
>>
>>" I measured on Windows with a Qt Creator built with
>> WebEngine support and surfed a little through the docs. The memory
>> consumpt
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
Approver rights have been set. Sorry for the delay (totally my fault)
--
Alex
From: Development on behalf of Volker
Hilsheimer
Sent: Thursday, 16 May 2019 4:45:19 PM
To: Qt development mailing list
Subject: [Development] Nominating Mikhail Svetkin for A
> On 26. Jun 2019, at 13:47, Simon Hausmann wrote:
>
> Hi,
>
> From my earlier email:
>
> " I measured on Windows with a Qt Creator built with
> WebEngine support and surfed a little through the docs. The memory
> consumption of the web engine process weighed in between 14-20 MB of RAM.
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
Message-ID: <20190626133856.518e070a
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 separate renderer process. Main process (in case for example
s
Hi,
>From my earlier email:
" I measured on Windows with a Qt Creator built with
WebEngine support and surfed a little through the docs. The memory
consumption of the web engine process weighed in between 14-20 MB of RAM."
That number came from the task manager in Windows.
Simon
___
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
ictly prohibited. If you have received this e-mail in
error, please immediately notify the sender by replying to this e-mail and then
delete this e-mail and any attachment(s) or copies thereof from your system.
Thank you.
-- next part --
A non-text attachment was scrubbed...
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
19 matches
Mail list logo
