[Development] Qml mime types

Knoll Lars Lars.Knoll at digia.com
Tue Dec 11 14:01:05 CET 2012


On Dec 11, 2012, at 10:48 AM, Mohamed Fawzi <Fawzi.Mohamed at digia.com> wrote:

> Now Qt has several files that use the QML syntax:
> 
> * .qml files of QtQuick 1 and QtQuick 2
> * .qbs files
> * .qmlproject files
> * .qmltypes files
> 
> I wanted to clean up a bit the mime types for the editor, and introduce q generic "QML syntax" file type.
> 
> I began doing it using the current application/x-qml type, but Marc Mutz said that it would be better to register types with iana as they did without too much effort for KOffice.
> 
> Indeed registering in the vendor tree (vnd.) seems to be doable, and I think it is a good idea.
> 
> I was thinking of registering 
> 	text/vnd.qt.qml => a file using the qml syntax, subclass of text/plain; charset=utf-8
> 
> and
> 	text/vnd.qt.qml-qtquick (.qml file)

I don't like this too much, as .qml doesn't have to imply using qt quick. Why not merge this with the generic text/vnd.qt.qml entry above?

> 	text/vnd.qt.qbs (.qbs file)
> 	text/vnd.qt.qml-project (.qmlproject)
> 	text/vnd.qt.qml-meta-info (.qmltypes)
> as subclasses of text/vnd.qt.qml
> 
These look ok to me.

> I would specify that the charset parameter should not be used in conjunction with these types, as they all use utf-8.
> This charset consideration respect the new guidelines for text/* mime types, that were done to address the concers that made (for example) application/javascript, or the "better choice", and introduced issues with html and xml.
> 
> I would no make the connection to text/javascript explicit, because there are subtle differences that makes that none is a perfect subset of the other (charset & strictness, vs extended syntax), but I am open to reconsider this.

Please don't try to connect them to text/javascript. I think that would cause more confusion then it's worth it. qml is not valid JS syntax after all.

Cheers,
Lars

> 
> This registration should be done for qt, so I am opening the discussion about them here, and when we have a consensus the proposal can be done on ietf-types at iana.org, and then officially registred at
> 	http://www.iana.org/cgi-bin/mediatypes.pl
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development




More information about the Development mailing list