organize qml files in subdirectories

This makes the organization of the qml files a bit more fine-grained, it
prevents mixing of .cpp and QML files, and also of what's compiled, and
what's included in the app as qrc data.

In particular:
- subsurface specific QML items go into the qml/ subdirectory
- theme and unit definitions to into qml/theme subdirectory (they
  already were located in a theme directory)
- generic components, such as our Label goes into qml/components

This facilitates sharing of functionality and identifying common stuff
better. Ideally, we can pull qml/theme and qml/components from a
standardized set at some point, so we don't have to maintain that code.

Signed-off-by: Sebastian Kügler <sebas@kde.org>
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>

1 files changed, 37 insertions, 0 deletions

diff --git a/qt-mobile/qml/TextButton.qml b/qt-mobile/qml/TextButton.qml
new file mode 100644
index 000000000..3e5a36735
--- /dev/null
+++ b/qt-mobile/qml/TextButton.qml
@@ -0,0 +1,37 @@
+import QtQuick 2.3
+
+Rectangle {
+	id: container
+
+	property alias text: label.text
+
+	signal clicked
+
+	width: label.width + 20; height: label.height + 6
+	smooth: true
+	radius: 10
+
+	gradient: Gradient {
+		GradientStop { id: gradientStop; position: 0.0; color: palette.light }
+		GradientStop { position: 1.0; color: palette.button }
+	}
+
+	SystemPalette { id: palette }
+
+	MouseArea {
+		id: mouseArea
+		anchors.fill: parent
+		onClicked: { container.clicked() }
+	}
+
+	Text {
+		id: label
+		anchors.centerIn: parent
+	}
+
+	states: State {
+		name: "pressed"
+		when: mouseArea.pressed
+		PropertyChanges { target: gradientStop; color: palette.dark }
+	}
+}