Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I had a suspicion that it was in there, but must be broken to cause P@t's problem. I'll check if the timer interval gets reset in that case - it should.

Edit: yes it is reset. I'll investigate properly when I get chance then.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I've noticed that the Timeline does not work anymore since a couple fw's ago :(
Anyone else noticed as well?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

No? What does it do?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I can't see the match scores and the prayertimes anymore. However, it did work before on an older version. Can't remember what version it was. Or is it because I have the newest fw on the watch now?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Could they have been left over from an android or iOS pairing? Because custom timeline items aren't supported yet - it all has to go through subscriptions on pebble.com. That'll be a major bit of work.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

That's weird... I really had some timeline features on the first few couple versions O_o

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

DeveloperConnection RPM went to beta. Don't forget to add websockets.

It also means it went with WebSockets API enabled in the JSkit - another thing to test.
CloudConnection proxy not implemented - only direct (lan) connectivity (--phone target).
PhoneAppLog is not yet implemented, watch log should work (as it uses relay feature).

In general since DevCon does not use any auth - it's actually quite a dangerous backdoor.
hence current behaviour is that it never starts automatically, should be enabled explicitly in the GUI.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

That's great news, will definitely try it out.

Any suggestions on how we could manage this QtWebSockets dependency in the main app? At the moment they'd have to explictly enable Coderus' repo, and upgraders won't catch that. Should I mirror it?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Well, yes, probably would make sense to prepare two rpms, with WS linked as a subproject, and _light_ rpm relying on external dependency. We could even slim static version down by removing declarative (qml) part.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Why are libs statically linked anyway? Compatibility? Using shared libraries could save a few precious kilobytes.