e Wit mailto:mark.de...@iesve.com>>;
development@qt-project.org<mailto:development@qt-project.org>
Subject: RE: [Development] Please do not remove QtWebkit from 5.6 official
binaries
Hi Mark,
If you need to use Qt Webkit, then it is probably better to stay with Qt 5.5.
There is n
lto:development@qt-project.org>
Subject: Re: [Development] Please do not remove QtWebkit from 5.6 official
binaries
On Dec 3, 2015, at 8:31 AM, Shaw Andy
mailto:andy.s...@theqtcompany.com>> wrote:
>There is QPdfWriter at least which is a paint device, so you could use that
>for
ton
Sent: 3. desember 2015 15:09
To: Mark De Wit
Cc: development@qt-project.org<mailto:development@qt-project.org>
Subject: Re: [Development] Please do not remove QtWebkit from 5.6 official
binaries
Will Qt 5.6 have alternative methods to export HTML to PDF that support major
platforms of Android, i
2015 13:31
To: Shaw Andy
Cc: Mark De Wit ; development@qt-project.org
Subject: Re: [Development] Please do not remove QtWebkit from 5.6 official
binaries
On Dec 3, 2015, at 8:31 AM, Shaw Andy
mailto:andy.s...@theqtcompany.com>> wrote:
>There is QPdfWriter at least which is a paint d
opment@qt-project.org>
Subject: Re: [Development] Please do not remove QtWebkit from 5.6 official
binaries
Will Qt 5.6 have alternative methods to export HTML to PDF that support major
platforms of Android, iOS, Linux, OS X, and Windows?
On iOS a Qt developer must resort to native co
tree/packaging-tools/releases
Mark
-Original Message-
From: Development [mailto:development-boun...@qt-project.org] On Behalf Of
Alejandro Exojo
Sent: 03 December 2015 19:08
To: development@qt-project.org
Subject: Re: [Development] Please do not remove QtWebkit from 5.6 official
binaries
El
El Thursday 03 December 2015, Mark De Wit escribió:
> Building from source would be an option, I guess. We have done it in the
> past, but the build process / flags (for distribution) is not sufficiently
> well documented, and starting with 5.5.1 we were excited to be able to use
> official binari
On Thursday 03 December 2015 18:13:58 Konstantin Tokarev wrote:
> > Instead, you should build this:
> > http://download.qt.io/official_releases/qt/5.5/5.5.1/submodules/qtwebkit-o
> > pensource-src-5.5.1.zip
> > http://download.qt.io/official_releases/qt/5.5/5.5.1/submodules/qtwebkit->
> > > openso
03.12.2015, 18:05, "Thiago Macieira" :
> On Thursday 03 December 2015 15:54:42 Konstantin Tokarev wrote:
>> > Besides being possible to use QtWebKit from 5.5 with Qt 5.6, there are
>> > also
>> > QtWebKit 5.6.0 sources in git, they are just not part of the official
>> > release.
>> Why not a
On Thursday 03 December 2015 15:54:42 Konstantin Tokarev wrote:
> > Besides being possible to use QtWebKit from 5.5 with Qt 5.6, there are
> > also
> > QtWebKit 5.6.0 sources in git, they are just not part of the official
> > release.
> Why not at least package its sources them same way as are sour
: development@qt-project.org
Subject: Re: [Development] Please do not remove QtWebkit from 5.6 official
binaries
Will Qt 5.6 have alternative methods to export HTML to PDF that support major
platforms of Android, iOS, Linux, OS X, and Windows?
On iOS a Qt developer must resort to native code to generate
@qt-project.org>
Subject: RE: [Development] Please do not remove QtWebkit from 5.6 official
binaries
Hi Mark,
If you need to use Qt Webkit, then it is probably better to stay with Qt 5.5.
There is nothing that makes Qt 5.5 bad overnight, if it works for you now. Qt
WebEngine is in many aspects a
Kind regards,
Mark
From: Turunen Tuukka [mailto:tuukka.turu...@theqtcompany.com]
Sent: 03 December 2015 12:30
To: Mark De Wit ; development@qt-project.org
Subject: RE: [Development] Please do not remove QtWebkit from 5.6 official
binaries
Hi Mark,
If you need to use Qt Webkit, then it is pro
03.12.2015, 15:41, "Allan Sandfeld Jensen" :
> On Thursday 03 December 2015, Mark De Wit wrote:
>> Hi all,
>>
>> QtWebEngine does not yet have feature parity with QtWebkit. For instance,
>> print support (especially export to PDF) is a critical requirement for my
>> use of Webkit. This missin
On Thursday 03 December 2015, Mark De Wit wrote:
> Hi all,
>
> QtWebEngine does not yet have feature parity with QtWebkit. For instance,
> print support (especially export to PDF) is a critical requirement for my
> use of Webkit. This missing feature prevents me from migrating to
> WebEngine.
>
] Please do not remove QtWebkit from 5.6 official binaries
Hi all,
QtWebEngine does not yet have feature parity with QtWebkit. For instance,
print support (especially export to PDF) is a critical requirement for my use
of Webkit. This missing feature prevents me from migrating to WebEngine.
Removing
Op 03/12/2015 om 12:18 schreef Mark De Wit:
Hi all,
QtWebEngine does not yet have feature parity with QtWebkit. For
instance, print support (especially export to PDF) is a critical
requirement for my use of Webkit. This missing feature prevents me
from migrating to WebEngine.
Removing
Hi all,
QtWebEngine does not yet have feature parity with QtWebkit. For instance,
print support (especially export to PDF) is a critical requirement for my use
of Webkit. This missing feature prevents me from migrating to WebEngine.
Removing webkit from the official distribution will prevent
18 matches
Mail list logo
