View Single Post
Posts: 287 | Thanked: 862 times | Joined on Dec 2015
#326
Originally Posted by ruff View Post
What are plans for proper timeline implementation? Started looking at how to hook in dev.con pin-ops and found complete absence of the timeline in rockpool. There's some rudimentary glue on top of blobdb to wrap calendar and notification events but otherwise it's empty.

I'm thinking about making something on top of sqlite to handle proper insert/select/update with either raw json or cooked serialized bytearray as a payload.
But this is big chunk of work, so if there's already movement in that direction somewhere else - can patiently wait or participate.
There's insertTimelinePin, which is how the calendar events are inserted, but that's the limit of what the app should be inserting.

I was told that watch apps can't insert pins into the timeline directly, but should use the user's account at Pebble as an aggregator. What should happen here is that the JS app makes a subscription request which is sent to pebble.com and opts the user into pins from that app, the watchapp developers push their pins there, and we pull them all together and insert them into the timeline. That would require an implementation of the login and account token that we spoke about before, and also a proper JSON representation of all pins, including the proper icon URLs. So far all there is for this are the empty methods in JSKitPebble: timelineSubscribe, timelineUnsubscribe, and getTimelineToken, but I think it's on RockWork's todo list as well.
 

The Following User Says Thank You to abranson For This Useful Post: