[Feature]: Bidirectional sync support.

[Excustic]

Is your feature request related to a problem?

Current syncing is done unidirectionally, meaning changes on OneNote are not transferred back to reMarkable.

Describe the solution you'd like

It should be possible to implement bidirectional syncing, though it won't be a trifle.
It will require:

• Creating some sort of trigger / listener on the host to detect changes made on OneNote. It would also require devising a sync strategy to prevent redundant consequent sync. (This could possibly be solved by manually syncing or introducing a trigger after a duration of several minutes of inactivity).
• Backing up .rm files
• A diffing mechanism to prevent loss of stroke data (like angle and pressure) and applying only new changes instead of overwriting everything.
• Patching rmc to enable InkML -> .rm conversion.
• Adding some visual cues on the application for backward sync events (OneNote -> reMarkable) + an option to turn it off on Settings tab.

This feature is not trivial to implement but definitely possible if done carefully.

[Fjoern]

How can I help with that?

[Excustic]

Hi @Fjoern, thanks for reaching out.

I think the first step is to create a POC of this feature by contributing directly to my rmc fork which is the core mechanism the project relies on.

Over there, a converter for InkML -> .rm can be implemented, as it is possible to generate .rm files manually. Naturally, there's a rm -> InkML converter implemented already which we can build upon. Once it's done, we can test and start integrating it into the project and figuring out the rest.

Feel free to open a pull request over there.

[Fjoern]

Hi,

thanks I will look into the repo and test a few things to help.