You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this only saves data in the browser there is no way to have 2 people working on the same diagram at the same time. But as a workaround it would be nice if I could save the diagram to a file in our repo, then when someone wants to edit / view it they can run a docker image locally that would read the file and load the diagram into the local instance. They would still need to export the file afterwords and commit unless there could be a feature to only read/write to a file instead of indexedDB.
The text was updated successfully, but these errors were encountered:
Actually there is a really messy implementation for some of the real time collaboration logic on the deprecated branch
The reason i didn't go through with it is because i couldn't think of a seamless way for 2 clients to communicate, since the diagrams get saved in the browser
E.g. if client 1 and client 2 join a room, edit the diagram, and client 1 disconnects and then connects back there is no way to merge client 2's changes without them having to share a new link
Any ideas about this would help, i might be missing something
Since this only saves data in the browser there is no way to have 2 people working on the same diagram at the same time. But as a workaround it would be nice if I could save the diagram to a file in our repo, then when someone wants to edit / view it they can run a docker image locally that would read the file and load the diagram into the local instance. They would still need to export the file afterwords and commit unless there could be a feature to only read/write to a file instead of indexedDB.
The text was updated successfully, but these errors were encountered: