> On 23 Jan 2018, at 15:11, Konstantin Tokarev wrote:
>
> 23.01.2018, 17:09, "Morten Sørvig" :
>>
>> The QtWebEngine requirement does seem to run counter to the purpose of the
>> QtWebView module.
>>
>> It’s not really clear from the history what happened, but I think we can
>> restore the or
23.01.2018, 17:09, "Morten Sørvig" :
>> On 22 Jan 2018, at 18:22, Alberto Mardegan
>> wrote:
>>
>> On 22/01/2018 18:49, Konstantin Tokarev wrote:
>>> From [1] it seems like QT_MAC_USE_NATIVE_WEBVIEW environment variable
>>> is required to use native backend.
>>>
>>> [1] https://codereview.
> On 22 Jan 2018, at 18:22, Alberto Mardegan
> wrote:
>
> On 22/01/2018 18:49, Konstantin Tokarev wrote:
>> From [1] it seems like QT_MAC_USE_NATIVE_WEBVIEW environment variable
>> is required to use native backend.
>>
>> [1] https://codereview.qt-project.org/#/c/162337/
>
> Yes, but still Q
On 22/01/2018 18:49, Konstantin Tokarev wrote:
> From [1] it seems like QT_MAC_USE_NATIVE_WEBVIEW environment variable
> is required to use native backend.
>
> [1] https://codereview.qt-project.org/#/c/162337/
Yes, but still QtWebEngine is required, as QtWebView is linking to it.
I've now removed
22.01.2018, 18:37, "Alberto Mardegan" :
> Hi all!
> I've developed a desktop application which uses the WebView QML
> module, with the hope of publishing it in the Apple store. However,
> unless I am seriously mistaken, this is just not possible (or maybe the
> documentation needs some serious
Hi all!
I've developed a desktop application which uses the WebView QML
module, with the hope of publishing it in the Apple store. However,
unless I am seriously mistaken, this is just not possible (or maybe the
documentation needs some serious love).
No matter what I try, it seems that QtWebEng
