introduce the AppMsgManager and the JsKitManager

will be used to handle application messages (push, etc)
while the JSKitManager will run PebbleKit JS scripts.

also add the ability to unpack PebbleDicts

1 files changed, 41 insertions, 0 deletions

diff --git a/daemon/jskitmanager.h b/daemon/jskitmanager.h
new file mode 100644
index 0000000..5e2880f
--- /dev/null
+++ b/daemon/jskitmanager.h
@@ -0,0 +1,41 @@
+#ifndef JSKITMANAGER_H
+#define JSKITMANAGER_H
+
+#include <QJSEngine>
+#include "appmanager.h"
+#include "appmsgmanager.h"
+
+class JSKitPebble;
+
+class JSKitManager : public QObject
+{
+    Q_OBJECT
+    LOG4QT_DECLARE_QCLASS_LOGGER
+
+public:
+    explicit JSKitManager(AppManager *apps, AppMsgManager *appmsg, QObject *parent = 0);
+    ~JSKitManager();
+
+signals:
+
+public slots:
+
+private slots:
+    void handleAppStarted(const QUuid &uuid);
+    void handleAppStopped(const QUuid &uuid);
+
+private:
+    void startJsApp();
+    void stopJsApp();
+
+private:
+    friend class JSKitPebble;
+
+    AppManager *_apps;
+    AppMsgManager *_appmsg;
+    AppManager::AppInfo _curApp;
+    QJSEngine *_engine;
+    QPointer<JSKitPebble> _jspebble;
+};
+
+#endif // JSKITMANAGER_H