[Development] Controlling QML Imports

Thiago Macieira thiago.macieira at intel.com
Tue Dec 11 05:30:39 CET 2012

On terça-feira, 11 de dezembro de 2012 13.43.08, Lincoln Ramsay wrote:
> On 11/12/12 13:23, Alan Alpert wrote:
> > Any comments on adding an API like this?
> > 
> > Are there any other usecases which this might need to support?
> If we're talking device security and restrictions policy... then please
> make this something that can fail "softly" at runtime.

Platform security policies cannot be handled by this functionality. If an 
application that runs native code requires security and restrictions, those 
need to be done at a level that applies to native code too.

If you're thinking of a QML runtime loader that does not load or run native 
code (QML files only), then this might work. But, to be honest, is this a 
realistic use-case? If we want a QML runtime, won't the platform want to allow 
loading of native plugins from the application?

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20121210/08272b4e/attachment.sig>

More information about the Development mailing list