Three days of hard work, but now the node.js service is completely implemented. The most parts of my js libraries could be transfered without many changes from the app to the node.js service. 🙂
Now the app merly is a gateway to the service, and we have done the first important step towards automatic synchronization in the background.
Sadly though, I renamed the service in early april. That, together with this nasty webOS bug hindered my service from working. Luckily only devices with the old, not working service with the old name installed are affected and I did the rename before I submitted the app to webos nation. So most people should be fine. 🙂
For the rest here are the instructions how to repair it:
- [Optional, step 3 might delte all data on the device] Install version 0.0.16 (get it from github) and do a sync of your data
- Install 0.1.1
- Execute sh /media/cryptofs/apps/usr/palm/applications/info.mobo.syncml.client/repairDBPermission.sh on a command line on the device, use novaterm or webosquickinstall or a ssh connection
- Run the app
- Maybe you need to configure the account again
- Anyway, run a sync with “Refresh-from-server” set.
The biggest improvement for the user right now is much cleaner logs. The majority of the logging is now done in the background to the file /media/internal/.info.mobo.syncml.log. In the app only some (hopefully) useful messages show up to give an impression of the status of the sync and what is working and what not. 🙂
Also the log is now send as attachement, which helps the webOS E-Mail app a lot. People can also get it via usb mode. It’s a great change, I think.
So… what next? Automatic background syncs? Or contacts?