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
Thanks to all who helped resolve the merge conflicts, and Liang who helped with
5.12->xxxs merges. Ah, and of course Mårten, the author of original patches.
Best regards,
Timur.
From: Volker Hilsheimer
Sent: Tuesday, June 25, 2019 8:55 PM
To: development@qt
Great work resolving this issue!
Volker
On 25 Jun 2019, at 20:13, Timur Pocheptsov
mailto:timur.pochept...@qt.io>> wrote:
5.13 is also good now.
Best regards,
Timur.
From: Development
mailto:development-boun...@qt-project.org>>
on behalf of Timur Pochept
5.13 is also good now.
Best regards,
Timur.
From: Development on behalf of Timur
Pocheptsov
Sent: Tuesday, June 25, 2019 6:51 PM
To: development@qt-project.org
Subject: Re: [Development] Failing auto-tests (SSL)
Update: 5.9 and dev are fixed now. Merge 5.12
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
Update: 5.9 and dev are fixed now. Merge 5.12->5.13 is still integrating.
Best regards,
Timur.
From: Timur Pocheptsov
Sent: Tuesday, June 25, 2019 10:23 AM
To: development@qt-project.org
Subject: Failing auto-tests (SSL)
Hi all,
The soon-expiring apache's cert
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 2019-05-06, 8:16 AM, "Development on behalf of Frederik Gladhorn"
wrote:
Hello,
We've been working on the Gerrit Upgrade for a while now and we are finally
getting ready to deploy the new goodness.
We have all patches in our fork (yes, sadly we continue diverging a
> 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
Hello,
That for sure doesn't account for complexity of what we are getting with this
move. Quite heavily stripped down version of chromium inside webengine has ~20M
loc, that is 10x times more than whole qtc. The actual browser is twice as big
in terms of loc. Official doc page for building Qt
On Tuesday, June 25, 2019 12:23:55 PM CEST Tor Arne Vestbø wrote:
> The name qtplatformdefinitions will likely quickly be wrong once something
> else needs to be dumped in there. How about just qtinfra?
> Tor Arne
>
I'm not really asking for "catch all" repository. I do not know why anything
Or qtqainfra 😊
> On 25 Jun 2019, at 12:23, Tor Arne Vestbø wrote:
>
> The name qtplatformdefinitions will likely quickly be wrong once something
> else needs to be dumped in there. How about just qtinfra?
>
> Tor Arne
>
>> On 25 Jun 2019, at 12:18, Jedrzej Nowacki wrote:
>>
>> As in: https
The name qtplatformdefinitions will likely quickly be wrong once something else
needs to be dumped in there. How about just qtinfra?
Tor Arne
> On 25 Jun 2019, at 12:18, Jedrzej Nowacki wrote:
>
> As in: https://bugreports.qt.io/browse/QTQAINFRA-3068
>
> We need a repository for infrastructu
As in: https://bugreports.qt.io/browse/QTQAINFRA-3068
We need a repository for infrastructure, so we do not need to abuse qt5
repository anymore.
Cheers,
Jędrek
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/li
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
Hi all,
The soon-expiring apache's certificate on our network test server was replaced
yesterday.
This was done too fast without properly fixing our tests/replacing the certs we
have locally. The affected tests are tst_qsslsocket/tst_qnetworkreply. As of
now - we fixed
the problem in 5.12 and st
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
Hi,
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?
Simon
From: Giuseppe D'Angelo
Sent: Tuesday, June 25, 2019 10:02
To: Simon Hausmann; development@qt-project.
> 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
Hi,
I don't think that support for x86 macOS will be retroactively added,
especially since upstream as well as Apple are dropping x86.
MinGW is also not a supported compiler, but it's possible to build with
clang-cl, which is what upstream is using. (Interestingly, Safari, FireFox and
Chrome a
Hi,
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 test, I just installed a fresh Windows 10 in Virtua
44 matches
Mail list logo
