this would allow cascade based stuff to use the same text/vnd.qt.qml type as 
the qt-quick one without it sounding strange, as the file type does not refer 
qt-quick.

Please not that I am not sure that this is the correct way to approach this, as 
I like that files that have to be handled differently have a different type.

Already now the qml/qtquick split creates some headaches for tooling, as the 
default imports for a file cannot be solved in isolation when one sees the 
file, but some heuristic is required looking at the imports.
This is made worse from things like webkit that is not versioned neither by 
appending the version number to the directory, nor in the qmldir, making it so 
that importing both will fail (code model can still works because it has the 
qmltypes, but other issues come up).

Fawzi
________________________________________
From: [email protected] 
[[email protected]] on behalf of 
Thiago Macieira [[email protected]]
Sent: Tuesday, December 11, 2012 5:08 PM
To: [email protected]
Subject: Re: [Development] Qml mime types

On terça-feira, 11 de dezembro de 2012 14.12.12, Mohamed Fawzi wrote:
>   text/vnd.qt.qml-base
> for the superclass of all files with qml syntax, and
>   text/vnd.qt.qml
> for the qml runtime specific files
> sound better?

How is that any different? What's a "qml runtime"?

--
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to