On Friday, 3 de June de 2011 05:08:15 Jason H wrote: > 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?
Several, but all solvable. It's mostly about Qt not playing very well being a
plugin to something else. Qt prefers to be in control and has been designed to
do that.
But if you think you can do it, you're welcome to start a project and research
the possibility.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
