CoPilot
CoPilot copied to clipboard
finestructure
Support publishing of multiple files or whole projects
Based on discussion in #44
Currently you can only publish files by navigating to the Edit menu and select Publish. If you want to collaborate on a whole project with many files this can be very tedious.
Things to consider:
- how do you publish a multiple files / a projects?
- how do you subscribe? You'd still need to bring up whatever editor is active "on the other side".
just a small thought.. i think the best way would be that any change that happens, actually happens in the servers "project", and my xcode tabs are just windows to his files (it shouldnt matter if the server has the file open or not. so when the copilot editing is done, the server can just push the changes and then everyone can pull. i think thats much simpler than syncing, and at the end everyone has the same changes, but only one should commit. does that make sense? i dont know if there is a simpler way to do that.. like shared folder or something maybe? i dont know how xcode handles it if you open a project twice.
Well, that sounds like a distributed version control system :) The way CoPilot works is that it exposes the text in an editor window via the network. It needs that editor window to apply the changes to and they're not saved unless you save - it's really just like typing in that window.
So the only way this would work in the context of CoPilot is if it auto-publishes new windows and the other party can open those easily. Note that when the publisher closes a window they are already unpublished. There's no other way to do it. The client still has the window and all its data but the place it's talking to is gone - so it cannot send (or receive) further updates. Instead you now have a local copy of the data.
From what you describe it seems like you want git but without the overhead of having to commit and that is indeed what CoPilot does. But it works on editor windows, not on files. I don't see a way around that but it could be easier to auto-expose new editor windows, allowing faster switching between files.
I hope that makes sense.
alright. i understand what you mean. thanks for explaining how copilot currently works. i wish you luck with this issue and with copilot in general. maybe we will meet again :)