[Development] Qml mime types

[Mohamed Fawzi]

Do I understand you correctly that you prefer my initial proposal with text/vnd.qt.qml at the top? or you want qml-base and qml as subtype?
Assuming you meant the first option we get to

text/plain; charset=utf-8
  text/vnd.qt.qml => a file written in the qml language
    text/vnd.qt.qtquick+qml  => .qml file like now: qtquick
    text/vnd.qt.qbs+qml => .qbs files
    text/vnd.qt.meta-info+qml => .qmltypes files
    text/vnd.qt.project+qml => .qmlproject files

Lars you were against this, did you change opinion in the meantime?

the other option would be

text/plain; charset=utf-8
  text/vnd.qt.qml-base => a file written in the qml syntax
    text/vnd.qt.qml  => a file written in the qml language
      text/vnd.qt.qtquick+qml  => .qml file like now: qtquick
    text/vnd.qt.qbs+qml => .qbs files
    text/vnd.qt.meta-info+qml => .qmltypes files
    text/vnd.qt.project+qml => .qmlproject files

but I wonder how to define exactly the difference between text/vnd.qt.qml-base text/vnd.qt.qml, so I am not convinced of this second option

Fawzi
________________________________________
From: Alan Alpert [416365416c at gmail.com]
Sent: Wednesday, December 12, 2012 10:18 PM
To: Mohamed Fawzi
Cc: Knoll Lars; faure at kde.org; development at qt-project.org
Subject: Re: [Development] Qml mime types

On Wed, Dec 12, 2012 at 2:59 AM, Mohamed Fawzi <Fawzi.Mohamed at digia.com> wrote:
> ...
> I propose the following hierarchy:
>
> text/plain; charset=utf-8
>    text/vnd.qt.qml-base : a file using the qml syntax in some context
>      text/vnd.qt.qml : the current .qml files
>      text/vnd.qt.qbs : a qbs file
>      text/vnd.qt.qml-meta-info : qmltypes meta info
>      text/vnd.qt.qml-project : a qmlproject file
>
> later we might want to split
> text/vnd.qt.qml in several subtypes (and probably own extensions) for example:
> text/vnd.qt.qml-qtquick1
> text/vnd.qt.qml-qtquick2
>   text/vnd.qt.qml-qq2-partial
>   text/vnd.qt.qml-qq2-full
>
> but I think it is better to leave that for another time, we just have to make sure that we can accomodate them in a reasonable way if/when the need arises.
>

Sorry for my fixation on file extensions. The point about generic qml
not being the same as the current .qml files remains valid though. So
I'd recommend we make text/vnd.qt.qml be "a file written in the qml
language" and let the current .qml files be text/vnd.qt.qml-qtquick1
already (or just text/vnd.qt.qtml-qtquick and split it up later). The
current .qml files containing snippets of a QtQuick scene is a legacy
convention, and not how the language should be perceived going
forwards. (Note that .qml files containing snippets of a QtQuick scene
is a usecase that should always be supported, it's just that the
language is growing beyond that as the sole usecase for QML.)

--
Alan Alpert