Originally proposed by @Nik777.
[Luke S's comments] Nik needs to decide how ambitious this feature is supposed to be. I see three basic choices, in accending order of difficulty:
In case of 2 or 3, could be implemented as:
- Peer-to-peer (all instances of AOI have full copies of the scene, and updates are traded back and forth.) - Selecting one instance as a server. All other instances become remote front ends for the server instance, sending commands, and it and only it directly mutates the scene graph.
The tools that would be necessary to get version 3 too work would also allow merging of independent, offline changes to an AOI scene. (think a primitive git merge for AOI files)
The server version, at least, would probably require decoupled UI (FR#355) though a decoupled UI would probably make all of these options easier.
What's the reason for building this into AoI, rather than just using a generic screen sharing utility?
I'm just turning ideas from the "What should we do for 3.x" thread into tickets... As I pointed out, Nik needs to clarify exactly how much the original idea was supposed to do. If all he wants to do is allow someone to shoulder-surf his workflow, screen-sharing (over skype, for example) would probably be just fine. (plus it would add a built-in voice channel.)
The other two options are a little more involved... Though, I do think that even they would be plugin territory.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.