[Qt5-feedback] Will there be browser plugins?

[Jason H]

While I appreciate the attempt, it's a flawed idea.

1. Locked in to chrome. (A WebKit platform)

2. Qt is too big to send to the client all the time. Better to deploy one version of Qt and have the whole web use that.

3. NACL only works on x86 architectures. NSAPI is native to the platform, leaving only platform independent resources to be loaded.


What's the problem with supporting NSAPI?



----- Original Message -----
From: "morten.sorvig at nokia.com" <morten.sorvig at nokia.com>
To: qt5-feedback at qt.nokia.com
Cc: 
Sent: Friday, June 3, 2011 7:20 AM
Subject: [Qt5-feedback] Will there be browser plugins?

Those of you who are interested in Qt as a browser plugin might want to take a look at Qt for Google Native Client research project (developer.qt.nokia.com/wiki/Qt_for_Google_Native_Client), which is Qt compiled as a sandboxed native client module using PPAPI ("Pepper" - Google's NPAPI alternative). 

The way this is different from the other plugin solutions mentioned is that there is no dependency on having QtWebkit or a Qt plugin installed - Qt is downloaded toghether with the application code. 

The port is currenly for Qt 4 only, but as far as I can see there is nothing in the Qt 5 design or requirements that would prevent porting. (Pepper OpenGL ES support is on its way for example).

Morten


_______________________________________________
Qt5-feedback mailing list
Qt5-feedback at qt.nokia.com
http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback