[Interest] QtWebkit replacement status...

[Ian Monroe]

nsapi has no future. For PDF just use a JavaScript viewer instead if the
PDFs need to be embedded into a web page, like what Firefox does. If they
aren't embedded it wouldn't take much to have your code detect that the
user click on a PDF url and do something smart.

Ian

On Mon, Mar 23, 2015 at 12:16 PM Jason Dolan <jason at pcc.com> wrote:

> I would love to hear some “official” input on this.  Our project will be
> migrating to Qt5 later on this year.  One of our 3rd-party services is
> embedded into our product as a webpage.  That 3rd-party makes use of nsapi
> plugins.  Primarily for pdf viewing.  We have then used QWebPluginFactory
> to create our own internal PDF viewer plugin (using poppler).  If we can’t
> do that in Qt5, that is going to be a problem.
>
> --
> Jason Dolan
> Software Developer
> PCC
> Control Your Future.
>
> 800-722-7708
> jason at pcc.com
> www.pcc.com
> twitter.com/pccvt
>
>
>
> On Mar 23, 2015, at 12:40 PM, Andreas Pakulat <apaku at gmx.de> wrote:
>
> Hi,
>
> On Mon, Mar 23, 2015 at 4:14 PM, Frank Hemer <frank at hemer.org> wrote:
>
>> Hi Scott,
>>
>> On Monday 23 March 2015 15:00:16 Scott Aron Bloom wrote:
>> > Which version of Qt should I use? 5.4?
>> >
>>
>> well, I currently use Qt5.4.0 with webkit since there recently have some
>> annoying bugs with the nsapi plugin been fixed.
>> The browser pdf plugins are a must for me (no alternative for using a pdf
>> reader on end user systems), so I must wait for webengine to provide a
>> replacement for these ... on devdays there has been mentioned that nsapi
>> support is not planned to be implemented so that makes me worry a bit ...
>>
>
> You may be out of luck on that, unless I'm mistaken QtWebEngine is based
> on the Chrome/Chromium code-base and that one has dropped nsapi support (
> http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html).
> That being said more recent versions of Chromium seem to include the
> pdf-plugin that was originally done for Google Chrome, so it may be just a
> matter of getting that part built and included (no idea which chromium
> version QtWebEngine uses right now).
>
> Andreas
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20150323/f526dc79/attachment.html>