[Development] Metadata for loading QML plugins (was: qmlbundle vs Qt Resource System)

Thiago Macieira thiago.macieira at intel.com
Wed Aug 14 20:33:39 CEST 2013

On quarta-feira, 14 de agosto de 2013 11:13:09, Alan Alpert wrote:
> > yes, it *must* be extended. you must make the system find the plugins
> > themselves, not the qmldir files.
> You've failed to convince me that this *must* happen. The current
> system works fine, this change would not fix the statically linked
> plugin case, and the only advantage I see is that we'd be able to use
> the JSON metadata - which is another change without any clear
> advantage. Considering the thread started by decrying 'work for the
> sake of it' I think we need some compelling reasons to make that
> change.

This discussion is not constructive anymore.

Alan, please explain what the QML engine needs when it finds a given import 
statement. Assume an "abstract could of plugins" and that you can get any 
information you'd like from that cloud.

Let's start with the ideal scenario and then we'll see what we can do.

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/20130814/d14c1a0e/attachment.sig>

More information about the Development mailing list