Fixed kolabnow account setup page.

The account plugin supplies the configuration UI, the application
supplies the scaffolding. That way we ensure the application doens't
contain any account specific code and account configurations are free to
offer specialized UI's that work best for them.
We're not currently using a standardized controller, but if we did those
controllers would have to live with the plugin, not the framework or the
components.

1 files changed, 3 insertions, 1 deletions

diff --git a/framework/accounts/accountfactory.h b/framework/accounts/accountfactory.h
index 047454ae..b57854e5 100644
--- a/framework/accounts/accountfactory.h
+++ b/framework/accounts/accountfactory.h
@@ -23,12 +23,13 @@
 #include <QVariant>
 
 /**
- * A factory to instantiate accountp plugins.
+ * A factory to instantiate account-plugins.
  */
 class AccountFactory : public QObject
 {
     Q_OBJECT
     Q_PROPERTY(QString accountId MEMBER mAccountId WRITE setAccountId);
+    Q_PROPERTY(QString accountType MEMBER mAccountType WRITE setAccountType);
     Q_PROPERTY(QString name MEMBER mName READ name NOTIFY accountLoaded);
     Q_PROPERTY(QString icon MEMBER mIcon NOTIFY accountLoaded);
     Q_PROPERTY(QString uiPath MEMBER mUiPath NOTIFY accountLoaded);
@@ -36,6 +37,7 @@ public:
     explicit AccountFactory(QObject *parent = Q_NULLPTR);
 
     void setAccountId(const QString &);
+    void setAccountType(const QString &);
     QString name() const;
 
 signals: