[Development] QML engine C++ class renaming
thiago.macieira at intel.com
Wed Feb 15 10:44:46 CET 2012
On quarta-feira, 15 de fevereiro de 2012 18.59.45, Alan Alpert wrote:
> > Q followed by lowercase letters used to be reserved for third-party
> > implementations. The Q in Qt classes means Qt itself, it's not the first
> > letter in another acronym. So these classes should actually be called
> > "QQml".
> The Q in QML means Qt itself. I'd be happy with QMlEngine if that floats
> your boat (except we probably aren't renaming everything again just to
> change capitalization :P ).
In "QmlFoo", the first three letters refer to the acronym or technology name
"QML", otherwise the m wouldn't be lowercase. I don't think we want to expand
the M because the word it stands for is just marketing and has little to do
with what the language is.
To be honest, QMLEngine is better than QmlEngine.
> The two theoretical cases which might have been compatible are non-graphical
> QML libraries (which I don't think exist yet) and really dumb QML launchers
> (which still probably should make a conscious switch to scenegraph as it
> involves a fundamental change in rendering that you ought to be prepared
Understood, thanks for clarifying.
> > One final question: is it possible for the Qt Quick 1 module to use the
> > Quick 2 language module (QT += qml) and simply wrap it with its
> > QDeclarative classes, retaining compatibility?
> There have been some incompatible changes, such as moving the local storage
> API out of the engine. While they haven't been that many, it would certainly
> not be a simple wrapping and you'd also lose a lot of 'bug compatibility'
> (in the 'behaviour change sense', not the 'stopped crashing' sense).
Ok. How does that affect the API and not the language itself?
How big are the Qt Quick 1 language support classes? I'm asking so we can have
an idea of how much maintenance effort those classes will be. I assume that
they will continue to use V8, which will be continually updated and modified to
support Qt Quick 2 and that introduces risk of regressions and breakages.
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 190 bytes
Desc: This is a digitally signed message part.
More information about the Development