View Single Post
Posts: 153 | Thanked: 159 times | Joined on Nov 2009
#22
Originally Posted by Bundyo View Post
The settings part is in fact in the UI part of the Pebble Android app No sure if we will need more than a JS engine in the daemon.
Yes the settings part is and should be in the ui part here too.
Problem is that the "companion" part also needs XMLHttpRequest and GPS thing which is not supported by QScriptEngine, only QWebkit

My idea would be doing the app handlers as a separate deamon and communicate with the main daemon. (dbus?)

The pebble js kit handler would be a separate deamon like one for SmartStatus+ for example.

The app deamon could be activated or suspended by the main daemon based on the launcher message (49) from the pebble (not sure if the message is sent reliable)