jabref
jabref copied to clipboard
JabRef
Synchronization with Overleaf
why was this bug closed? was a solution implemented, or was the idea rejected for some reason?
The issue was put on hold. That means we try to focus on other issues first due to lack of resources. However, I developed a generally working solution which needs still to be improved before it can be used. See #2866 for details.
I don't think I can close this issue, but I'll be starting with export and "Push entries to external application (Overleaf)" features next week and see if I can get some inspiration for the synchronization issue meanwhile.
I'll see if I can continue on https://github.com/koppor/jabref/pull/445 afterwards.
@k3KAW8Pnf7mkmdSMPHz27 That is really nice! I wrote the initial feature years ago and recently reworked it to successfully connect to overleaf. Might look complicated at first 😏 The general logic is that JabRef establishes/hooks into the web socket connection that overleaf uses to report changes. It's working bidirectional. Key challenge is to apply the incoming changes from overleaf which are character positions relative to the start of the document and not on a per entry basis.
@k3KAW8Pnf7mkmdSMPHz27 Nice to hear! My main concerns are written there https://github.com/JabRef/jabref/pull/2866#issuecomment-388264343. You can reach me via mail or skype (same user name). Let's discuss details.
I don't think I can close this issue, but I'll be starting with export and "Push entries to external application (Overleaf)" features next week
I think, this is already implemented in https://github.com/koppor/jabref/pull/445, isn't it?
Related work regarding synchronization: https://github.com/JabRef/jabref/pull/5669
With the part at https://github.com/JabRef/jabref/issues/7618#issuecomment-845543064, we came up with a solution how optimistic offline lock also works for locally stored files. We did not came up with an idea in 2015.