Collaboration conflicts about freeplane-collaborative-addon HOT 3 OPEN

Hi, gruz. I'll be working intensively for the next month on a system that may incorporate this project and may drive some revisions. We share your concerns. Are you available to help develop or test? Here are some ideas we are considering as steps toward solving this:
-convert the maps to canonical XML before writing to disk so that diff works better
-save each node to a separate file (supports some other goals I have) reducing the diff conflicts to something more easily resolved programmatically
-use something like the "construct from deltas" techniques that Apache Wave uses to manage concurrent edits (Wave is designed for this purpose and was donated to Apache by Google who developed it further for Google Docs; I am not sure of the readiness of that code, though)

I welcome collaborators on solving these issues, whether from Sebastian, gruz, or anyone else!

from freeplane-collaborative-addon.

Hi Liam.

Sorry to say this, but I don't work with mindmaps nowadays. So I can help with some test cases if you provide them and there is nobody else. But at least now I don't need the tool and have low motivation to work with something I don't use. You'd be better find someone, who is currently interested in the tool and is ready to invest own time into it.

from freeplane-collaborative-addon.

@LiamDGray : I think that the first approach to store a canonical XML would indeed improve diff, however I am not sure that this can be implemented in a plugin. You may need to contribute to the core.

Not sure that saving each node to a separate file would help. And it is certainly a bit hard to implement because it would have many side effects.

The last option "construct from deltas" is the better IMHO as would enable a realtime collaboration solution. However it requires development in the freeplane core I think.

from freeplane-collaborative-addon.