subject:"\[Development\] Please do not remove QtWebkit from 5.6 official binaries"

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-05 Thread Knoll Lars



On 03/12/15 15:09, "Development on behalf of Edward Sutton" 
<development-boun...@qt-project.org<mailto:development-boun...@qt-project.org> 
on behalf of edward.sut...@subsite.com<mailto:edward.sut...@subsite.com>> wrote:

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 PDF files.

Unfortunately Qt 5.5 PDF export is dependent on QPrinter which is not supported 
on iOS.  While iOS can create and displays PDF’s just fine, iOS has no printer 
support.


In the future, Is it possible the PDF creation dependency could be separated 
from QPrinter?  So that Qt PDF generation would have better cross-platform 
support?


QPrinter printer(QPrinter::ScreenResolution); // QPrinter not supported on 
iOS

printer.setOutputFormat(QPrinter::PdfFormat);

printer.setOutputFileName(pdfFileName);

drawReport(printer);

m_painter.end();


Without understanding internals of PDF file creation, it feels like PDF 
creation should not be dependent on QPrinter?

We have an alternative to using QPrinter since Qt 5.0. Please have a look at 
QPdfWriter. It's in Qt Gui, fully platform independent and should just work on 
iOS.

Cheers,
Lars



-Ed


On Dec 3, 2015, at 7:37 AM, Mark De Wit 
<mark.de...@iesve.com<mailto:mark.de...@iesve.com>> wrote:

Thanks for all the feedback everyone.

We are excited about the 5.6 release because we are looking closely at the new 
Qt3D module, as well as migrating to VS 2015.  Sadly, PDF export of HTML 
content is a critical feature for our product (in general I’m happy to move to 
WebEngine, but we cannot remove output functionality from our software).

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 
binaries.

Kind regards,
Mark

From: Turunen Tuukka [mailto:tuukka.turu...@theqtcompany.com]
Sent: 03 December 2015 12:30
To: Mark De Wit <mark.de...@iesve.com<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 nothing that makes Qt 5.5 bad overnight, if it works for you now. Qt 
WebEngine is in many aspects already much better in features than Qt Webkit. Qt 
WebEngine is also better maintained, and does receive much more improvements 
and security fixes than Qt Webkit. Even though some features of Qt WebKit are 
not in same way available with Qt WebEngine, it is overall a better choice. Qt 
Webkit is removed from Qt 5.6 because it is no longer maintained well enough to 
be part of an official Qt release. We are also not developing and testing it to 
work with Qt 5.6.

Yours,

  Tuukka

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of Mark 
De Wit
Sent: torstaina 3. joulukuuta 2015 13.18
To: development@qt-project.org<mailto:development@qt-project.org>
Subject: [Development] 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 webkit from the official distribution will prevent me (and surely 
others) from upgrading to 5.6.

Thanks,
Mark
___
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

This email and any files transmitted with it from The Charles Machine Works, 
Inc. are confidential and intended solely for the use of the individual or 
entity to which they are addressed. If you have received this email in error 
please notify the sender. Our company accepts no liability for the contents of 
this email, or for the consequences of any actions taken on the basis of the 
information provided, unless that information is subsequently confirmed in 
writing. Please note that any views or opinions presented in this email are 
solely those of the author and do not necessarily represent those of the 
company. Finally, the recipient should check this email and any attachments for 
the presence of viruses. The company accepts no liability for any damage caused 
by any virus transmitted by this email.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-04 Thread Mark De Wit

Hmm, interesting, I wasn't aware of that location.  However, I don't think 
those flags are right, hasn't OpenGL switched to be Dynamic instead of Desktop, 
for instance?

Having looked around further, I'm liking the look of this:

http://code.qt.io/cgit/qtsdk/qtsdk.git/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 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 binaries.

When reproducing a build, I always start with the flags in this repository:

http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config

--
Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2
http://barnacity.net/ | http://disperso.net 
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-04 Thread Edward Sutton

On Dec 3, 2015, at 8:31 AM, Shaw Andy 
<andy.s...@theqtcompany.com<mailto:andy.s...@theqtcompany.com>> wrote:

>There is QPdfWriter at least which is a paint device, so you could use that 
>for generating PDFs as that is available iOS from what I can see.

I *really* need to spend some time browsing All 
Classes<http://doc.qt.io/qt-5/classes.html>  !

http://doc.qt.io/qt-5/classes.html

Thanks again Andy!

-Ed

Andy

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of 
Edward Sutton
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, iOS, Linux, OS X, and Windows?

On iOS a Qt developer must resort to native code to generate PDF files.

Unfortunately Qt 5.5 PDF export is dependent on QPrinter which is not supported 
on iOS.  While iOS can create and displays PDF’s just fine, iOS has no printer 
support.

In the future, Is it possible the PDF creation dependency could be separated 
from QPrinter?  So that Qt PDF generation would have better cross-platform 
support?

QPrinter printer(QPrinter::ScreenResolution); // QPrinter not supported on 
iOS

printer.setOutputFormat(QPrinter::PdfFormat);

printer.setOutputFileName(pdfFileName);

drawReport(printer);

m_painter.end();

Without understanding internals of PDF file creation, it feels like PDF 
creation should not be dependent on QPrinter?

-Ed

On Dec 3, 2015, at 7:37 AM, Mark De Wit 
<mark.de...@iesve.com<mailto:mark.de...@iesve.com>> wrote:

Thanks for all the feedback everyone.

We are excited about the 5.6 release because we are looking closely at the new 
Qt3D module, as well as migrating to VS 2015.  Sadly, PDF export of HTML 
content is a critical feature for our product (in general I’m happy to move to 
WebEngine, but we cannot remove output functionality from our software).

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 
binaries.

Kind regards,
Mark

From: Turunen Tuukka [mailto:tuukka.turu...@theqtcompany.com]
Sent: 03 December 2015 12:30
To: Mark De Wit <mark.de...@iesve.com<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 nothing that makes Qt 5.5 bad overnight, if it works for you now. Qt 
WebEngine is in many aspects already much better in features than Qt Webkit. Qt 
WebEngine is also better maintained, and does receive much more improvements 
and security fixes than Qt Webkit. Even though some features of Qt WebKit are 
not in same way available with Qt WebEngine, it is overall a better choice. Qt 
Webkit is removed from Qt 5.6 because it is no longer maintained well enough to 
be part of an official Qt release. We are also not developing and testing it to 
work with Qt 5.6.

Yours,

  Tuukka

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of Mark 
De Wit
Sent: torstaina 3. joulukuuta 2015 13.18
To: development@qt-project.org<mailto:development@qt-project.org>
Subject: [Development] 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 webkit from the official distribution will prevent me (and surely 
others) from upgrading to 5.6.

Thanks,
Mark
___
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

This email and any files transmitted with it from The Charles Machine Works, 
Inc. are confidential and intended solely for the use of the individual or 
entity to which they are addressed. If you have received this email in error 
please notify the sender. Our company accepts no liability for the contents of 
this email, or for the consequences of any actions taken on the basis of the 
information provided, unless that information is subsequently confirmed in 
writing. Please note that any views or opinions presented in this email are 
solely those of the author and do not necessarily represent those of the 
company. Finally, the recipient should check this email and any attachments for 
the presence of viruses. The company accepts no

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-04 Thread Edward Sutton

On Dec 4, 2015, at 7:53 AM, Mark De Wit 
<mark.de...@iesve.com<mailto:mark.de...@iesve.com>> wrote:

>We tried this solution already in combination with WebEngine.  It draws a 
>bitmap of the current view into the PDF.  Even text gets rendered as bitmaps, 
>it is a far cry from supporting our multi-page HTML documents.

I may have tried QPdfWriter once as well and had issues with sizing and 
scaling.  I know I spent a *lot* of time with cross-platform PDF generation 
development.

Rendering PDF report text as bitmaps would not be acceptable to my customers 
either.

Not good news for developers that must create PDFs on iOS.

-Ed

Mark

From: Edward Sutton [mailto:edward.sut...@subsite.com]
Sent: 04 December 2015 13:31
To: Shaw Andy <andy.s...@theqtcompany.com<mailto:andy.s...@theqtcompany.com>>
Cc: Mark De Wit <mark.de...@iesve.com<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

On Dec 3, 2015, at 8:31 AM, Shaw Andy 
<andy.s...@theqtcompany.com<mailto:andy.s...@theqtcompany.com>> wrote:

>There is QPdfWriter at least which is a paint device, so you could use that 
>for generating PDFs as that is available iOS from what I can see.

I *really* need to spend some time browsing All 
Classes<http://doc.qt.io/qt-5/classes.html>  !

http://doc.qt.io/qt-5/classes.html

Thanks again Andy!

-Ed

Andy

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of 
Edward Sutton
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, iOS, Linux, OS X, and Windows?

On iOS a Qt developer must resort to native code to generate PDF files.

Unfortunately Qt 5.5 PDF export is dependent on QPrinter which is not supported 
on iOS.  While iOS can create and displays PDF’s just fine, iOS has no printer 
support.

In the future, Is it possible the PDF creation dependency could be separated 
from QPrinter?  So that Qt PDF generation would have better cross-platform 
support?

QPrinter printer(QPrinter::ScreenResolution); // QPrinter not supported on 
iOS

printer.setOutputFormat(QPrinter::PdfFormat);

printer.setOutputFileName(pdfFileName);

drawReport(printer);

m_painter.end();

Without understanding internals of PDF file creation, it feels like PDF 
creation should not be dependent on QPrinter?

-Ed

On Dec 3, 2015, at 7:37 AM, Mark De Wit 
<mark.de...@iesve.com<mailto:mark.de...@iesve.com>> wrote:

Thanks for all the feedback everyone.

We are excited about the 5.6 release because we are looking closely at the new 
Qt3D module, as well as migrating to VS 2015.  Sadly, PDF export of HTML 
content is a critical feature for our product (in general I’m happy to move to 
WebEngine, but we cannot remove output functionality from our software).

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 
binaries.

Kind regards,
Mark

From: Turunen Tuukka [mailto:tuukka.turu...@theqtcompany.com]
Sent: 03 December 2015 12:30
To: Mark De Wit <mark.de...@iesve.com<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 nothing that makes Qt 5.5 bad overnight, if it works for you now. Qt 
WebEngine is in many aspects already much better in features than Qt Webkit. Qt 
WebEngine is also better maintained, and does receive much more improvements 
and security fixes than Qt Webkit. Even though some features of Qt WebKit are 
not in same way available with Qt WebEngine, it is overall a better choice. Qt 
Webkit is removed from Qt 5.6 because it is no longer maintained well enough to 
be part of an official Qt release. We are also not developing and testing it to 
work with Qt 5.6.

Yours,

  Tuukka

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of Mark 
De Wit
Sent: torstaina 3. joulukuuta 2015 13.18
To: development@qt-project.org<mailto:development@qt-project.org>
Subject: [Development] 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

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-04 Thread Mark De Wit

We tried this solution already in combination with WebEngine.  It draws a 
bitmap of the current view into the PDF.  Even text gets rendered as bitmaps, 
it is a far cry from supporting our multi-page HTML documents.

Mark

From: Edward Sutton [mailto:edward.sut...@subsite.com]
Sent: 04 December 2015 13:31
To: Shaw Andy <andy.s...@theqtcompany.com>
Cc: Mark De Wit <mark.de...@iesve.com>; 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 
<andy.s...@theqtcompany.com<mailto:andy.s...@theqtcompany.com>> wrote:

>There is QPdfWriter at least which is a paint device, so you could use that 
>for generating PDFs as that is available iOS from what I can see.

I *really* need to spend some time browsing All 
Classes<http://doc.qt.io/qt-5/classes.html>  !

http://doc.qt.io/qt-5/classes.html

Thanks again Andy!

-Ed

Andy

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of 
Edward Sutton
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, iOS, Linux, OS X, and Windows?

On iOS a Qt developer must resort to native code to generate PDF files.

Unfortunately Qt 5.5 PDF export is dependent on QPrinter which is not supported 
on iOS.  While iOS can create and displays PDF’s just fine, iOS has no printer 
support.

In the future, Is it possible the PDF creation dependency could be separated 
from QPrinter?  So that Qt PDF generation would have better cross-platform 
support?

QPrinter printer(QPrinter::ScreenResolution); // QPrinter not supported on 
iOS

printer.setOutputFormat(QPrinter::PdfFormat);

printer.setOutputFileName(pdfFileName);

drawReport(printer);

m_painter.end();

Without understanding internals of PDF file creation, it feels like PDF 
creation should not be dependent on QPrinter?

-Ed

On Dec 3, 2015, at 7:37 AM, Mark De Wit 
<mark.de...@iesve.com<mailto:mark.de...@iesve.com>> wrote:

Thanks for all the feedback everyone.

We are excited about the 5.6 release because we are looking closely at the new 
Qt3D module, as well as migrating to VS 2015.  Sadly, PDF export of HTML 
content is a critical feature for our product (in general I’m happy to move to 
WebEngine, but we cannot remove output functionality from our software).

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 
binaries.

Kind regards,
Mark

From: Turunen Tuukka [mailto:tuukka.turu...@theqtcompany.com]
Sent: 03 December 2015 12:30
To: Mark De Wit <mark.de...@iesve.com<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 nothing that makes Qt 5.5 bad overnight, if it works for you now. Qt 
WebEngine is in many aspects already much better in features than Qt Webkit. Qt 
WebEngine is also better maintained, and does receive much more improvements 
and security fixes than Qt Webkit. Even though some features of Qt WebKit are 
not in same way available with Qt WebEngine, it is overall a better choice. Qt 
Webkit is removed from Qt 5.6 because it is no longer maintained well enough to 
be part of an official Qt release. We are also not developing and testing it to 
work with Qt 5.6.

Yours,

  Tuukka

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of Mark 
De Wit
Sent: torstaina 3. joulukuuta 2015 13.18
To: development@qt-project.org<mailto:development@qt-project.org>
Subject: [Development] 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 webkit from the official distribution will prevent me (and surely 
others) from upgrading to 5.6.

Thanks,
Mark
___
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

This email and any files transmitted with it from The Charles Machine Works, 
Inc. are confidential and intended solely for the use of the individual or 
entity to which they are addressed. If you have received this email i

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-04 Thread Shaw Andy

It wasn’t meant to be seen as a viable solution for rendering from QtWebEngine 
at least, but more for if you were already rending to a QPrinter with QPainter. 
If you use drawText() and so forth then that should work with QPdfWriter in a 
way that makes the text be rendered as text in the PDF. If this is not 
happening then please report it as it should be handled correctly in that 
instance.

Andy

From: Edward Sutton [mailto:edward.sut...@subsite.com]
Sent: 4. desember 2015 15:07
To: Mark De Wit
Cc: Shaw Andy; development@qt-project.org
Subject: Re: [Development] Please do not remove QtWebkit from 5.6 official 
binaries

On Dec 4, 2015, at 7:53 AM, Mark De Wit 
<mark.de...@iesve.com<mailto:mark.de...@iesve.com>> wrote:

>We tried this solution already in combination with WebEngine.  It draws a 
>bitmap of the current view into the PDF.  Even text gets rendered as bitmaps, 
>it is a far cry from supporting our multi-page HTML documents.

I may have tried QPdfWriter once as well and had issues with sizing and 
scaling.  I know I spent a *lot* of time with cross-platform PDF generation 
development.

Rendering PDF report text as bitmaps would not be acceptable to my customers 
either.

Not good news for developers that must create PDFs on iOS.

-Ed

Mark

From: Edward Sutton [mailto:edward.sut...@subsite.com]
Sent: 04 December 2015 13:31
To: Shaw Andy <andy.s...@theqtcompany.com<mailto:andy.s...@theqtcompany.com>>
Cc: Mark De Wit <mark.de...@iesve.com<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

On Dec 3, 2015, at 8:31 AM, Shaw Andy 
<andy.s...@theqtcompany.com<mailto:andy.s...@theqtcompany.com>> wrote:

>There is QPdfWriter at least which is a paint device, so you could use that 
>for generating PDFs as that is available iOS from what I can see.

I *really* need to spend some time browsing All 
Classes<http://doc.qt.io/qt-5/classes.html>  !

http://doc.qt.io/qt-5/classes.html

Thanks again Andy!

-Ed

Andy

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of 
Edward Sutton
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, iOS, Linux, OS X, and Windows?

On iOS a Qt developer must resort to native code to generate PDF files.

Unfortunately Qt 5.5 PDF export is dependent on QPrinter which is not supported 
on iOS.  While iOS can create and displays PDF’s just fine, iOS has no printer 
support.

In the future, Is it possible the PDF creation dependency could be separated 
from QPrinter?  So that Qt PDF generation would have better cross-platform 
support?

QPrinter printer(QPrinter::ScreenResolution); // QPrinter not supported on 
iOS

printer.setOutputFormat(QPrinter::PdfFormat);

printer.setOutputFileName(pdfFileName);

drawReport(printer);

m_painter.end();

Without understanding internals of PDF file creation, it feels like PDF 
creation should not be dependent on QPrinter?

-Ed

On Dec 3, 2015, at 7:37 AM, Mark De Wit 
<mark.de...@iesve.com<mailto:mark.de...@iesve.com>> wrote:

Thanks for all the feedback everyone.

We are excited about the 5.6 release because we are looking closely at the new 
Qt3D module, as well as migrating to VS 2015.  Sadly, PDF export of HTML 
content is a critical feature for our product (in general I’m happy to move to 
WebEngine, but we cannot remove output functionality from our software).

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 
binaries.

Kind regards,
Mark

From: Turunen Tuukka [mailto:tuukka.turu...@theqtcompany.com]
Sent: 03 December 2015 12:30
To: Mark De Wit <mark.de...@iesve.com<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 nothing that makes Qt 5.5 bad overnight, if it works for you now. Qt 
WebEngine is in many aspects already much better in features than Qt Webkit. Qt 
WebEngine is also better maintained, and does receive much more improvements 
and security fixes than Qt Webkit. Even though some features of Qt WebKit are 
not in same way available with Qt WebEngine, it is overall a better choice. Qt 
Webkit is removed from Qt 5.6 because it is no longer maintained well enoug

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-03 Thread Konstantin Tokarev



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 missing feature prevents me from migrating to
>>  WebEngine.
>>
>>  Removing webkit from the official distribution will prevent me (and surely
>>  others) from upgrading to 5.6.
>
> 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 sources of Qt add-ons?

-- 
Regards,
Konstantin
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-03 Thread André Somers




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 webkit from the official distribution will prevent me (and 
surely others) from upgrading to 5.6.



You should still be able to build QtWebkit against 5.6 if I understand 
it correctly, so you can still upgrade if you want. It does take more 
effort though.


André

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-03 Thread Turunen Tuukka


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 already much better in features than Qt Webkit. Qt 
WebEngine is also better maintained, and does receive much more improvements 
and security fixes than Qt Webkit. Even though some features of Qt WebKit are 
not in same way available with Qt WebEngine, it is overall a better choice. Qt 
Webkit is removed from Qt 5.6 because it is no longer maintained well enough to 
be part of an official Qt release. We are also not developing and testing it to 
work with Qt 5.6.

Yours,

  Tuukka

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of Mark 
De Wit
Sent: torstaina 3. joulukuuta 2015 13.18
To: development@qt-project.org
Subject: [Development] 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 webkit from the official distribution will prevent me (and surely 
others) from upgrading to 5.6.

Thanks,
Mark
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-03 Thread 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 missing feature prevents me from migrating to
> WebEngine.
> 
> Removing webkit from the official distribution will prevent me (and surely
> others) from upgrading to 5.6.
> 
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.

Regards
`Allan
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-03 Thread Mark De Wit

Thanks for all the feedback everyone.

We are excited about the 5.6 release because we are looking closely at the new 
Qt3D module, as well as migrating to VS 2015.  Sadly, PDF export of HTML 
content is a critical feature for our product (in general I'm happy to move to 
WebEngine, but we cannot remove output functionality from our software).

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 
binaries.

Kind regards,
Mark

From: Turunen Tuukka [mailto:tuukka.turu...@theqtcompany.com]
Sent: 03 December 2015 12:30
To: Mark De Wit <mark.de...@iesve.com>; 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 nothing that makes Qt 5.5 bad overnight, if it works for you now. Qt 
WebEngine is in many aspects already much better in features than Qt Webkit. Qt 
WebEngine is also better maintained, and does receive much more improvements 
and security fixes than Qt Webkit. Even though some features of Qt WebKit are 
not in same way available with Qt WebEngine, it is overall a better choice. Qt 
Webkit is removed from Qt 5.6 because it is no longer maintained well enough to 
be part of an official Qt release. We are also not developing and testing it to 
work with Qt 5.6.

Yours,

  Tuukka

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of Mark 
De Wit
Sent: torstaina 3. joulukuuta 2015 13.18
To: development@qt-project.org<mailto:development@qt-project.org>
Subject: [Development] 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 webkit from the official distribution will prevent me (and surely 
others) from upgrading to 5.6.

Thanks,
Mark
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-03 Thread Shaw Andy

There is QPdfWriter at least which is a paint device, so you could use that for 
generating PDFs as that is available iOS from what I can see.

Andy

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of 
Edward Sutton
Sent: 3. desember 2015 15:09
To: Mark De Wit
Cc: 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 PDF files.

Unfortunately Qt 5.5 PDF export is dependent on QPrinter which is not supported 
on iOS.  While iOS can create and displays PDF’s just fine, iOS has no printer 
support.

In the future, Is it possible the PDF creation dependency could be separated 
from QPrinter?  So that Qt PDF generation would have better cross-platform 
support?

QPrinter printer(QPrinter::ScreenResolution); // QPrinter not supported on 
iOS

printer.setOutputFormat(QPrinter::PdfFormat);

printer.setOutputFileName(pdfFileName);

drawReport(printer);

m_painter.end();

Without understanding internals of PDF file creation, it feels like PDF 
creation should not be dependent on QPrinter?

-Ed

On Dec 3, 2015, at 7:37 AM, Mark De Wit 
<mark.de...@iesve.com<mailto:mark.de...@iesve.com>> wrote:

Thanks for all the feedback everyone.

We are excited about the 5.6 release because we are looking closely at the new 
Qt3D module, as well as migrating to VS 2015.  Sadly, PDF export of HTML 
content is a critical feature for our product (in general I’m happy to move to 
WebEngine, but we cannot remove output functionality from our software).

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 
binaries.

Kind regards,
Mark

From: Turunen Tuukka [mailto:tuukka.turu...@theqtcompany.com]
Sent: 03 December 2015 12:30
To: Mark De Wit <mark.de...@iesve.com<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 nothing that makes Qt 5.5 bad overnight, if it works for you now. Qt 
WebEngine is in many aspects already much better in features than Qt Webkit. Qt 
WebEngine is also better maintained, and does receive much more improvements 
and security fixes than Qt Webkit. Even though some features of Qt WebKit are 
not in same way available with Qt WebEngine, it is overall a better choice. Qt 
Webkit is removed from Qt 5.6 because it is no longer maintained well enough to 
be part of an official Qt release. We are also not developing and testing it to 
work with Qt 5.6.

Yours,

  Tuukka

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of Mark 
De Wit
Sent: torstaina 3. joulukuuta 2015 13.18
To: development@qt-project.org<mailto:development@qt-project.org>
Subject: [Development] 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 webkit from the official distribution will prevent me (and surely 
others) from upgrading to 5.6.

Thanks,
Mark
___
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

This email and any files transmitted with it from The Charles Machine Works, 
Inc. are confidential and intended solely for the use of the individual or 
entity to which they are addressed. If you have received this email in error 
please notify the sender. Our company accepts no liability for the contents of 
this email, or for the consequences of any actions taken on the basis of the 
information provided, unless that information is subsequently confirmed in 
writing. Please note that any views or opinions presented in this email are 
solely those of the author and do not necessarily represent those of the 
company. Finally, the recipient should check this email and any attachments for 
the presence of viruses. The company accepts no liability for any damage caused 
by any virus transmitted by this email.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-03 Thread Edward Sutton

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 PDF files.

Unfortunately Qt 5.5 PDF export is dependent on QPrinter which is not supported 
on iOS.  While iOS can create and displays PDF’s just fine, iOS has no printer 
support.


In the future, Is it possible the PDF creation dependency could be separated 
from QPrinter?  So that Qt PDF generation would have better cross-platform 
support?


QPrinter printer(QPrinter::ScreenResolution); // QPrinter not supported on 
iOS

printer.setOutputFormat(QPrinter::PdfFormat);

printer.setOutputFileName(pdfFileName);

drawReport(printer);

m_painter.end();


Without understanding internals of PDF file creation, it feels like PDF 
creation should not be dependent on QPrinter?

-Ed


On Dec 3, 2015, at 7:37 AM, Mark De Wit 
<mark.de...@iesve.com<mailto:mark.de...@iesve.com>> wrote:

Thanks for all the feedback everyone.

We are excited about the 5.6 release because we are looking closely at the new 
Qt3D module, as well as migrating to VS 2015.  Sadly, PDF export of HTML 
content is a critical feature for our product (in general I’m happy to move to 
WebEngine, but we cannot remove output functionality from our software).

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 
binaries.

Kind regards,
Mark

From: Turunen Tuukka [mailto:tuukka.turu...@theqtcompany.com]
Sent: 03 December 2015 12:30
To: Mark De Wit <mark.de...@iesve.com<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 nothing that makes Qt 5.5 bad overnight, if it works for you now. Qt 
WebEngine is in many aspects already much better in features than Qt Webkit. Qt 
WebEngine is also better maintained, and does receive much more improvements 
and security fixes than Qt Webkit. Even though some features of Qt WebKit are 
not in same way available with Qt WebEngine, it is overall a better choice. Qt 
Webkit is removed from Qt 5.6 because it is no longer maintained well enough to 
be part of an official Qt release. We are also not developing and testing it to 
work with Qt 5.6.

Yours,

  Tuukka

From: Development [mailto:development-boun...@qt-project.org] On Behalf Of Mark 
De Wit
Sent: torstaina 3. joulukuuta 2015 13.18
To: development@qt-project.org<mailto:development@qt-project.org>
Subject: [Development] 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 webkit from the official distribution will prevent me (and surely 
others) from upgrading to 5.6.

Thanks,
Mark
___
Development mailing list
Development@qt-project.org<mailto:Development@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

This email and any files transmitted with it from The Charles Machine Works, 
Inc. are confidential and intended solely for the use of the individual or 
entity to which they are addressed. If you have received this email in error 
please notify the sender. Our company accepts no liability for the contents of 
this email, or for the consequences of any actions taken on the basis of the 
information provided, unless that information is subsequently confirmed in 
writing. Please note that any views or opinions presented in this email are 
solely those of the author and do not necessarily represent those of the 
company. Finally, the recipient should check this email and any attachments for 
the presence of viruses. The company accepts no liability for any damage caused 
by any virus transmitted by this email.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-03 Thread Thiago Macieira

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-> 
> > > opensource-src-5.5.1.tar.gz
> No, thanks, I need features which I've contributed to 5.6 branch.

You can compile your own version of qtwebkit, no problem. I have my own 
patches to it.

That doesn't mean they will be released.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-03 Thread 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 at least package its sources them same way as are sources of Qt
> add-ons?

Because we decided not to. We should not even have created the 5.6 branch on 
that repository, because there will be no 5.6.0 release. The changes that 
landed on that branch will remain forever unreleased.

Instead, you should build this:
http://download.qt.io/official_releases/qt/5.5/5.5.1/submodules/qtwebkit-opensource-src-5.5.1.zip
http://download.qt.io/official_releases/qt/5.5/5.5.1/submodules/qtwebkit-opensource-src-5.5.1.tar.gz

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-03 Thread Konstantin Tokarev



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 at least package its sources them same way as are sources of Qt
>>  add-ons?
>
> Because we decided not to. We should not even have created the 5.6 branch on
> that repository, because there will be no 5.6.0 release. The changes that
> landed on that branch will remain forever unreleased.
>
> Instead, you should build this:
> http://download.qt.io/official_releases/qt/5.5/5.5.1/submodules/qtwebkit-opensource-src-5.5.1.zip
> http://download.qt.io/official_releases/qt/5.5/5.5.1/submodules/qtwebkit-opensource-src-5.5.1.tar.gz

No, thanks, I need features which I've contributed to 5.6 branch.

-- 
Regards,
Konstantin
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

2015-12-03 Thread Alejandro Exojo

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 binaries.

When reproducing a build, I always start with the flags in this repository:

http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config

-- 
Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2
http://barnacity.net/ | http://disperso.net
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

Re: [Development] Please do not remove QtWebkit from 5.6 official binaries

17 matches

Site Navigation

Mail list logo

Footer information