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, 5 insertions, 15 deletions

diff --git a/components/package/contents/ui/EditAccountDialog.qml b/components/package/contents/ui/EditAccountDialog.qml
index 19349f38..a7461640 100644
--- a/components/package/contents/ui/EditAccountDialog.qml
+++ b/components/package/contents/ui/EditAccountDialog.qml
@@ -21,28 +21,18 @@ import QtQuick.Layouts 1.1
 
 import org.kde.kirigami 1.0 as Kirigami
 
-import org.kube.framework.settings 1.0 as KubeSettings
-import org.kube.framework.domain 1.0 as KubeFramework
 import org.kube.components 1.0 as KubeComponents
 
 KubeComponents.OverlayDialog {
-    id: root
+    id: dialog
 
-    property variant uiSource
     property variant accountId
+    EditAccount {
+        accountId: dialog.accountId
 
-    Item {
-        id: dialog
         anchors.centerIn: parent
 
-        height: root.height * 0.8
-        width: root.width * 0.8
-
-        Loader {
-            anchors.fill: parent
-
-            source: root.uiSource
-            onLoaded: item.accountId = root.accountId
-        }
+        height: dialog.height * 0.8
+        width: dialog.width * 0.8
     }
 }