Use enumerations for detail types and detail fields.

This patch changes the internal representation of detail
types and field names within details from a string-based
representation to enum constants.
Detail definition names are then replaced by the
concept of "Detail Type".
Enum values are also aligned across C++ Vs QML APIs

Authors:
- Tommi Anttila <tommi.4.anttila@nokia.com>
- Claudio Brunelli <claudio.brunelli@nokia.com>
- Cristiano di Flora <cristiano.di-flora@nokia.com>

Change-Id: I8b86022d08f9c3baf84b658f07e6600efdc73b8b
Reviewed-by: Cristiano di Flora <cristiano.di-flora@nokia.com>
Reviewed-by: Claudio Brunelli <claudio.brunelli@nokia.com>

1 files changed, 3 insertions, 13 deletions

diff --git a/src/imports/contacts/details/qdeclarativecontacttag_p.h b/src/imports/contacts/details/qdeclarativecontacttag_p.h
index 45cba879a..3a26a6023 100644
--- a/src/imports/contacts/details/qdeclarativecontacttag_p.h
+++ b/src/imports/contacts/details/qdeclarativecontacttag_p.h
@@ -56,7 +56,7 @@ class QDeclarativeContactTag : public QDeclarativeContactDetail
     Q_CLASSINFO("DefaultProperty", "tag")
 public:
     enum FieldType {
-        Tag = 0
+        Tag = QContactTag::FieldTag
     };
 
     QDeclarativeContactTag(QObject* parent = 0)
@@ -65,21 +65,11 @@ public:
         setDetail(QContactTag());
         connect(this, SIGNAL(valueChanged()), SIGNAL(detailChanged()));
     }
-    ContactDetailType detailType() const
+    DetailType detailType() const
     {
         return QDeclarativeContactDetail::Tag;
     }
-    static QString fieldNameFromFieldType(int fieldType)
-    {
-        switch (fieldType) {
-        case Tag:
-            return QContactTag::FieldTag;
-        default:
-            break;
-        }
-        qmlInfo(0) << tr("Unknown field type.");
-        return QString();
-    }
+
     void setTag(const QString& v)
     {
         if (!readOnly() && v != tag()) {