If that approach is simpler, perhaps two helper scripts or executables could be triggered, somehow "hooked" into Leo's save and load routines, so that after a save the data is imported into the DB, and before a load it's exported.
Let the user choose if it's done A "every save/load", B just when opening and closing Leo or C disabled (handled manually by the user). The more frequently it's done the less frequent sync issues will arise - I reckon that's going to be one of the difficult hurdles, handling conflicts when a node has changed both locally and via the DB between sync's. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/EqdgngSFYLEJ. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
