Why do we keep the pointless QGS* prefix for QML classes?

[Michael Hasselmann]

Hi,

as graphics view is on its way out, with Qt Quick 2, I was wondering why
QML still keeps (then-to-be) historical link to it, through its QGS
prefix for its base classes.

I mean, isn't also one of the Qt API guidelines to avoid abbreviations
where possible? I personally think that QSceneItem would for example be
a better fit than QSGItem (same for QSGPaintedItem).

Opinions?

[Alan Alpert]

Post by Michael Hasselmann
Hi,
as graphics view is on its way out, with Qt Quick 2, I was wondering why
QML still keeps (then-to-be) historical link to it, through its QGS
prefix for its base classes.
I mean, isn't also one of the Qt API guidelines to avoid abbreviations
where possible? I personally think that QSceneItem would for example be
a better fit than QSGItem (same for QSGPaintedItem).

This was brought up last week on this very list. Not that it can't be
discussed further, but Aaron has already answered your question.

Post by Michael Hasselmann
Hi,

Hi,
I didn't have time to play with QtQuick2 yet, but looking at the code
I think there are some points that should be reconsidered.
1. Naming conventions
QtQuick2 items adopts an abbreviation 'SG' to prefix their class
names, like QSGItem. Since SG is not a well know acronym, wouldn't be
better to have a more descriptive name without abbreviating? Like,
QQuickItem, QSceneItem or even QSceneGraphItem?

"SG" is a placeholder. The plan is to rename QSGItem to QQuickItem.

[Michael Hasselmann]

Post by Alan Alpert

Post by Michael Hasselmann
Hi,
as graphics view is on its way out, with Qt Quick 2, I was wondering why
QML still keeps (then-to-be) historical link to it, through its QGS
prefix for its base classes.
I mean, isn't also one of the Qt API guidelines to avoid abbreviations
where possible? I personally think that QSceneItem would for example be
a better fit than QSGItem (same for QSGPaintedItem).

This was brought up last week on this very list. Not that it can't be
discussed further, but Aaron has already answered your question.

Right, am sorry for not searching the archives. To my defense, this list
is very high volume and coming back from holiday doesn't make it easier
to deal with the amount of the feedback on this list ;-)

thanks,
Michael