Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I still have a general problem with some JS apps that are using the status constants in XMLHttpRequest - for some reason they always seem to be undefined no matter what I try. Misfit seems to still be broken because of this, and I hope Trello will be the same.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Here's a request: I'm a bit stuck with the language files. I know where to get them from, but I have no idea how to upload them to the watch. I've tried the existing uploadFile and even tried system resources, but just get NACKs from the watch. If anyone is set up to watch the android app do it, could you tell me what goes on during language file upload? I don't have an android device to try.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I've got an Android tablet and some spare time, so if you can explain how to do it (or link to the right docs, assuming it's easy enough to figure out)...

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Are you getting nacks starting from the very first packet (initialization) or for consequent data? i.e. the former would look strange as it means any upload should be failing, while the later is logicac if we're not using proper upload->type - eg. pebble just cannot parse incoming bytes in accordance with specified type and hence is failing and nacking the transfer.
I presume you've been trying with UploadTypeSystemResources? Did you try feeding the file to pbpack tool to check whether it's in proper binary resource format pebble understands?

I tried File and SystemResources. Have to manually calculate the CRC because it's not in the file, but I think it's right. I get the NACK after the upload is finished.

The timeline pin stuff is looking really good! That's exactly how Katharine said it should be, especially if we fetch the layout json from the pbz when we upgrade.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Try to enable DevCon and use pebble logs -vv --phone <phone.ip> to get live log feed. It also prints out pebble logs which it receives by eavesdropping watch connection - so maybe it'll spit out some clue.

The timeline - am currently working on the PoC phase2 - which is to create persistent pins (and storage). Once done - will move calendar events from CalendarEvent to json pins. As well as moving to nemo-qml-plugin-calendar (as hinted in the organizeradapter.cpp).
Phase3 will be to create authentication and finally websync.

With this in mind - can I ask for a change freeze on the notification/calendar mechanics while I'm slashing the sources?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Great, thanks. I still haven't really looked into the DevCon thing, I'll give it a try.

I was already waiting for this change before doing anything on the notifications or any other timeline bits. Everything I want to try requires more actions than are currently supported. I've also delayed any more pushes back to RockWork until this is done and all the vestiges cleaned up because I've got a feeling it'll be a lot simpler afterwards.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I bet it's about canned messages? %) I'm also itching to inject the actions - that's why i'm currently reworking action handlers (as part of new pin engine) and only then planning to finish persistence

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Dismissing and snoozing reminders too! Are they included?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Partly and not correctly, but the thing is that calendar reminders are system generated, so to snooze/dismiss system calendar reminders you need to snooze them in system calendar. And that part is completely missing in current implementation. That will be bound the the calendar migration to nemo-plugin-calendar - eg. (NemoCalendarEventModification::setReminder(NemoCa lendarEvent::ReminderNone))