On October 21, 2015 11:33:32 AM Matt McCutchen via mobileorg-android
<
mobileorg-android+APn2wQeSh-7OTX...@googlegroups.com>
wrote:
> For now, I'm using a simple patch (attached) that skips the entire pull
> with a notification only if edits are being pushed on the same
> synchronization. This should work as long as I see the notification before
> synchronizing again.
I'm at some pains to imagine how to handle it better than this (not that it
matters, as I'm only a user, not a developer of this tool).
If it's a new node, it would be reasonable to keep it in the phone until
the node comes back in a sync operation after pushing on the computer --
that is:
1. Make a new node on the phone.
2. The computer has auto-synced some changes.
3. In mobileorg on the phone, do a sync. This brings in new stuff from the
computer. Currently this also deletes new stuff from the phone. For the
sake of argument, let's pretend that it leaves new content in the phone.
4. Further updates in the computer, then org-mobile-push (C-c C-x RET p).
5. Sync again on the phone.
Step 5 should remove the new content saved locally in the phone and replace
it with the pushed material from the computer. But how do you match it up?
The user may have made any change to the headline text, or moved the
headline elsewhere in the file (or even into another file), and mobileorg
on the phone has no knowledge of, or control over, it. I guess you could
add a MOBILEORG_ID property with a GUID in the phone, but you can't
guarantee that the user won't remove it or tamper with it on the computer.
This isn't an answer, but I hope at least an acknowledgment that
mobileorg's current behavior is because it's a Difficult Problem.
hjh
Sent with AquaMail for Android
http://www.aqua-mail.com