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
I see that situation has improved somewhat since I've last tried to use
cppreference qch in Qt Creator about a year ago, but the formatting still
sometimes goes crazy (especially with "since C++XY" in the overload list),
and there are some issues with font aliasing. I.e. there are definitely
many w
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 that these are "beastly" numbers for
> deskt
24.06.2019, 15:46, "Simon Hausmann" :
> Am 24.06.19 um 12:31 schrieb Eike Ziller:
>>> * What exactly is so big about WebEngine? What is this size that many are
>>> hinting at but won't provide the number?
>> My numbers on macOS:
>>
>> WebEngineCore.framework = 145 MB
>> Current Qt Creator ap
> 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 a little through the docs. The memory
> consumption of the web e
Am 24.06.19 um 12:31 schrieb Eike Ziller:
>> * What exactly is so big about WebEngine? What is this size that many are
>> hinting at but won't provide the number?
> My numbers on macOS:
>
> WebEngineCore.framework = 145 MB
> Current Qt Creator application = 430 MB (and about 60 MB of this we curr
> On 24. Jun 2019, at 11:42, Palaraja, Kavindra wrote:
>
>
> On 24.06.19, 11:20, "Eike Ziller" wrote:
>
> ..
>
>> Have you seen Qt Creator's Help Integration recently?
>> * It doesn't render 1:1 with the default style that is used on
>> https://doc.qt.io
>
>Yes, the style has to be c
On 24.06.19, 11:20, "Eike Ziller" wrote:
..
> Have you seen Qt Creator's Help Integration recently?
> * It doesn't render 1:1 with the default style that is used on
https://doc.qt.io
Yes, the style has to be changed for QTextBrowser. Partly that is a
limitation of QTextBrowser (
24.06.2019, 12:23, "Eike Ziller" :
>> On 24. Jun 2019, at 08:20, Palaraja, Kavindra wrote:
>>
>> Hi Andre,
>>
>> I'm really curious -- why is it bad to make WebEngine mandatory for
>> anything that passes as "Qt Creator's Help Integration”?
>
> - QtWebEngine is a big beast
> - and browsing h
> On 24. Jun 2019, at 08:20, Palaraja, Kavindra wrote:
>
> Hi Andre,
>
> I'm really curious -- why is it bad to make WebEngine mandatory for anything
> that passes as "Qt Creator's Help Integration”?
- QtWebEngine is a big beast
- and browsing help only needs a small subset of the actual fea
16 matches
Mail list logo
