maemo.org - Talk
Page 3 of 59 12 3 4513 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   [SFOS] [Announce] Pebble Watch Connector daemon (https://talk.maemo.org/showthread.php?t=93399)

Bundyo 2014-07-03 20:57
Re: [Announce] Pebble Watch Connector daemon 0.2
 
Quote:
Originally Posted by smoku (Post 1431673)
I'm OK with embedding JavascriptCore in a daemon.
I'm not OK with embedding full-blown browser in a daemon. ;)
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.

smurfy 2014-07-04 13:05
Re: [Announce] Pebble Watch Connector daemon 0.2
 
Quote:
Originally Posted by Bundyo (Post 1431762)
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)

smoku 2014-07-04 13:40
Re: [Announce] Pebble Watch Connector daemon 0.2
 
Quote:
Originally Posted by smurfy (Post 1431812)
Problem is that the "companion" part also needs XMLHttpRequest and GPS thing which is not supported by QScriptEngine
These are easy enough to code in C++.

Quote:
Originally Posted by smurfy (Post 1431812)
My idea would be doing the app handlers as a separate deamon and communicate with the main daemon. (dbus?)
I see no reason to split them into separate processes. Just adds another layer of complication.

smurfy 2014-07-04 15:12
Re: [Announce] Pebble Watch Connector daemon 0.2
 
Was just an idea to not bloat the main deamon with app handlers the user probably don't use.

I still would suggesst adding some kind of dbus interface to allow third party apps to communicate with pebble.

smoku 2014-07-04 15:20
Re: [Announce] Pebble Watch Connector daemon 0.2
 
Quote:
Originally Posted by smurfy (Post 1431829)
Was just an idea to not bloat the main deamon with app handlers the user probably don't use.
AFAIU the idea is to load JS "companion app" only for the time when the "watch app" is active on Pebble. When user closes the watch app, the companion app is unloaded.


Quote:
Originally Posted by smurfy (Post 1431829)
I still would suggesst adding some kind of dbus interface to allow third party apps to communicate with pebble.
Good, but unrelated, idea. :)

smurfy 2014-07-05 11:28
Re: [Announce] Pebble Watch Connector daemon 0.2
 
Great.

I looked at the app and had some problems with it.

1. 99% of the time it does not show the caller id. I noticed that it seams to be a problem with the dbus thing. lineId is empty. But dbus-monitor shows the lineId. (probably getAll vs get)
2. The app does not work. (always no watch found) while the daemon connects and at least call notifications get triggered
3. I have problems compiling. While compiling "lib" i get warnings but it does compile:
Code:
ln: creating symbolic link `libpebble.so': Read-only file system
make: [libpebble.so.1.0.0] Error 1 (ignored)
ln: creating symbolic link `libpebble.so.1': Read-only file system
make: [libpebble.so.1.0.0] Error 1 (ignored)
ln: creating symbolic link `libpebble.so.1.0': Read-only file system
make: [libpebble.so.1.0.0] Error 1 (ignored)
And daemon/app fails to link with
Code:
"/opt/cross/bin/armv7hl-meego-linux-gnueabi-ld: cannot find -lpebble"
I use windows and the virtualbox mersdk to compile.

Any tips?

smoku 2014-07-05 18:08
Re: [Announce] Pebble Watch Connector daemon 0.2
 
1. I get that too, but very rarely. Possibly a Nemo bug.

2. I broke it in 0.2. Already fixed in 0.3.

3. These errors are very weird. Possibly some issues with your SDK. Do you have it freshly installed or upgraded from some earlier Alpha?

smurfy 2014-07-05 22:39
Re: [Announce] Pebble Watch Connector daemon 0.2
 
Ok,

about the compile problem:

With Virtual Box 4.1.8 creating symlinks on shares is disabled.
After enabling it, it still does not work, "protocol error", i guess thats because i use windows as host.

Copying the libpebble.so.1.0.0 to libpebble.so manually works and daemon and app now compiles.

smoku 2014-07-06 01:45
Re: [Announce] Pebble Watch Connector daemon 0.2
 
Quote:
Originally Posted by smurfy (Post 1431885)
2. The app does not work. (always no watch found) while the daemon connects and at least call notifications get triggered
Was it working for you in 0.1?

I'm pretty sure it was working fine in 0.1 with daemon running, but I cannot reproduce it now.
I always have a resource busy error when app tries to connect to pebble. Looks like I cannot open two concurrent connections to Pebble. Even when I downgraded to 0.1. Strange. I'm (pretty) sure it was working before...

MaemoUser 2014-07-07 07:31
Re: [Announce] Pebble Watch Connector daemon 0.2
 
I have no Pebble yet, so excuse the maybe dumb question ;).

Is it possible to install an application to the Pebble like Twebble and use it via your lib?


All times are GMT. The time now is 05:00.
Page 3 of 59 12 3 4513 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8