It doesn't happen often, but periodically I will edit the same note on my phone or tablet and on my PC without giving time for automatic syncs to catch up and without doing a manual sync and I (understandably) end up with a note in conflict.
The difficulty is that sometimes it is several months or even a year before I notice that the conflict occurred! I don't naturally think to go searching in the "Conflicting Changes" folder - I have a bunch of folders and there's nothing there to catch my eye so I just ignore it. I just now found a conflicted change from more than a year ago that actually caused some problems in a project because I was missing some key information (I knew I had entered the info but then when I went to look the information wasn't there and so I tried to cobble something together without my primary sources [which I had tossed after copying] and now I had this mess of inaccuracies in my primary note - now I find the actual information I was supposed to have in there in a note in my "Conflicting Changes" folder.)
Tools for diff/patch (tools to merge changes from 2 different branches off the same root as long as the changes occur in different areas of the document) are absolutely ubiquitous in this day and age. And the vast proportion of conflicting changes are going to be in separate areas of the note (I add a line at the beginning on one platform and re-word a sentence in the middle and delete a line at the end of the note) which should be child's play to merge.
For those changes which do occur close to one another, don't silently create a copy of the offending conflict! That's worse than nothing!
Instead, *inside the same copy of the note that I am viewing - the copy that remains in my primary folder* put some textual indicator of what was in one copy and what was in the other with lots of colorful exclamation points or otherwise to attract attention. Then, to be complete, place *both* original copies in the "Conflicting Changes" folder, referenced from the textual clues in the main note so the user knows that there was a problem and knows where to look to see what was in each copy.
===(snip)===
this is a change that was added in branch #1 and copied in - no conflict
these are
some intervening lines
this is a change that was made in branch #2 and merged in - conflict resolved
these are
some more
intervening
lines
!!!!!!!========CHANGES WERE MADE ON SEPARATE COPIES OF THIS NOTE AND EVERNOTE IS UNABLE TO RESOLVE THE CHANGES=========!!!!!!!
!!!!!!!===PLEASE SEE BELOW FOR DETAILS===!!!!!!!
!!!!!!!===ORIGINAL TEXT===!!!!!!
some context
This was my line in the original before any changes were made
some more context
!!!!!!!===TEXT AFTER CHANGES ON PC "xyz"===!!!!!!
some context
This is my line that I changed on my PC
some more context
!!!!!!!===TEXT AFTER CHANGES ON ANDROID DEVICE "abc"===!!!!!!
some context
This is my line that I changed on my android
some more context
!!!!!!===END OF CHANGES===!!!!!!!
!!!!!!===COPIES OF THE ORIGINAL NOTE AND BOTH CHANGED COPIES HAVE BEEN PLACED IN THE FOLDER "Conflicting Changes" with these titles:===!!!!!!
!!!!!!===Hello World - original before changes made - last updated 2015-10-02 13:52:32 ===!!!!!!!
!!!!!!===Hello World - with changes made on 2015-10-08 1:08:32pm from PC "xyz"===!!!!!!!
!!!!!!===Hello World - with changes made on 2015-10-08 1:12:32pm from ANDROID DEVICE "abc"===!!!!!!!
!!!!!!===After you have resolved the conflicting changes these additional copies of the note in "Conflicted Changes" should be deleted===!!!!!!!
more lines
just to fill up space
===(snip)===
When I see that it is abundantly clear exactly what I am supposed to do and there's no possibility that I can lose information as long as I am paying even a small amount of attention to what is going on in my note. It's the moral equivalent of what the linux utility "patch" does, but spelled out in color and with lots of words to help non-technical people understand what's going on.
Or, alternately (and perhaps more intuitively) pull up a dialog box each time the user opens EN or accesses the conflicted note which alerts the user to the fact that a conflict occurred and gives the opportunity to go through a wizard interface to choose how the final copy should look.
Idea
pbowers 2
It doesn't happen often, but periodically I will edit the same note on my phone or tablet and on my PC without giving time for automatic syncs to catch up and without doing a manual sync and I (understandably) end up with a note in conflict.
The difficulty is that sometimes it is several months or even a year before I notice that the conflict occurred! I don't naturally think to go searching in the "Conflicting Changes" folder - I have a bunch of folders and there's nothing there to catch my eye so I just ignore it. I just now found a conflicted change from more than a year ago that actually caused some problems in a project because I was missing some key information (I knew I had entered the info but then when I went to look the information wasn't there and so I tried to cobble something together without my primary sources [which I had tossed after copying] and now I had this mess of inaccuracies in my primary note - now I find the actual information I was supposed to have in there in a note in my "Conflicting Changes" folder.)
Tools for diff/patch (tools to merge changes from 2 different branches off the same root as long as the changes occur in different areas of the document) are absolutely ubiquitous in this day and age. And the vast proportion of conflicting changes are going to be in separate areas of the note (I add a line at the beginning on one platform and re-word a sentence in the middle and delete a line at the end of the note) which should be child's play to merge.
For those changes which do occur close to one another, don't silently create a copy of the offending conflict! That's worse than nothing!
Instead, *inside the same copy of the note that I am viewing - the copy that remains in my primary folder* put some textual indicator of what was in one copy and what was in the other with lots of colorful exclamation points or otherwise to attract attention. Then, to be complete, place *both* original copies in the "Conflicting Changes" folder, referenced from the textual clues in the main note so the user knows that there was a problem and knows where to look to see what was in each copy.
===(snip)===
this is a change that was added in branch #1 and copied in - no conflict
these are
some intervening lines
this is a change that was made in branch #2 and merged in - conflict resolved
these are
some more
intervening
lines
!!!!!!!========CHANGES WERE MADE ON SEPARATE COPIES OF THIS NOTE AND EVERNOTE IS UNABLE TO RESOLVE THE CHANGES=========!!!!!!!
!!!!!!!===PLEASE SEE BELOW FOR DETAILS===!!!!!!!
!!!!!!!===ORIGINAL TEXT===!!!!!!
some context
This was my line in the original before any changes were made
some more context
!!!!!!!===TEXT AFTER CHANGES ON PC "xyz"===!!!!!!
some context
This is my line that I changed on my PC
some more context
!!!!!!!===TEXT AFTER CHANGES ON ANDROID DEVICE "abc"===!!!!!!
some context
This is my line that I changed on my android
some more context
!!!!!!===END OF CHANGES===!!!!!!!
!!!!!!===COPIES OF THE ORIGINAL NOTE AND BOTH CHANGED COPIES HAVE BEEN PLACED IN THE FOLDER "Conflicting Changes" with these titles:===!!!!!!
!!!!!!===Hello World - original before changes made - last updated 2015-10-02 13:52:32 ===!!!!!!!
!!!!!!===Hello World - with changes made on 2015-10-08 1:08:32pm from PC "xyz"===!!!!!!!
!!!!!!===Hello World - with changes made on 2015-10-08 1:12:32pm from ANDROID DEVICE "abc"===!!!!!!!
!!!!!!===After you have resolved the conflicting changes these additional copies of the note in "Conflicted Changes" should be deleted===!!!!!!!
more lines
just to fill up space
===(snip)===
When I see that it is abundantly clear exactly what I am supposed to do and there's no possibility that I can lose information as long as I am paying even a small amount of attention to what is going on in my note. It's the moral equivalent of what the linux utility "patch" does, but spelled out in color and with lots of words to help non-technical people understand what's going on.
Or, alternately (and perhaps more intuitively) pull up a dialog box each time the user opens EN or accesses the conflicted note which alerts the user to the fact that a conflict occurred and gives the opportunity to go through a wizard interface to choose how the final copy should look.
13 replies to this idea
Recommended Posts
Archived
This topic is now archived and is closed to further replies.