Thu May 19, 2011 4:22 am Post
Thu May 19, 2011 7:12 pm Post
Thu May 19, 2011 8:18 pm Post
narrsd wrote:Dan, the thing is, doing this would unfortunately then reinvent the problem.
Whenever the files in a Scrivener project are separated, then Dropbox can and will create the differently-named 'conflict files', every time two or more Dropbox contents are changed.
Then portions of text, and also whole scrivenings, depenwill be apparently lost.
That's the problem we're trying to assure won't happen in future, and the only way that logically will do it, as far as I can see, is:
- have the Scrivener projects in single files
- do a manual merge of the enclosed projects, whenever Dropbox indicates that these single files have accumulated mutual differences from the original, which it will do by making its renamed copies.
Fri May 20, 2011 1:21 am Post
Fri May 20, 2011 6:45 am Post
Fri May 20, 2011 8:01 am Post
Fri May 20, 2011 2:13 pm Post
Fri May 20, 2011 3:57 pm Post
danwdoo wrote:I like the thought of knowing nothing will be messing with my files, but having an offline backup is crucial. Ultimately, it would be nice to have an automatic 'backup on Scrivener exit' feature so it drops a backup of the project into the drop box folder anytime I close the program (or at other scheduleable intervals). The downside would be a brief (hopefully) pause on exit while this is done. It's doable with other tools, so it's certainly not a mission critical feature but it would be nice.
Fri Jun 17, 2011 12:27 am Post
AmberV wrote:This all seems to more a job for .tar, than .zip. Compression is nice when you need to preserve space, so it is great for backups, but for a working format---I guess I don't get the point of compression, either. That's a ton of processing overhead, and it would effectively cripple auto-save for even a small-ish project of 20mb. Tar is a lot faster, and it's pretty easy to extract and update individual component elements on the fly. It would still be slower than a file-system by a long shot, but in most scenarios the slow-down would be barely noticeable---and presumably anyone using this method would be aware of the fact that one huge file is not going to be as much of a performance demon as files and folders.
Sun Jul 10, 2011 6:58 pm Post
Sun Jul 10, 2011 7:10 pm Post
Wed Oct 05, 2011 2:35 am Post
Wed Oct 05, 2011 2:41 am Post
For colaborations, you still need to impose discipline and work practices, like portioning out work. That way, only one person is changing a file or files. Break your colaboration into several scrivener projects, one per collaborator. Then one of you acts as project manager/librarian, and handles the merging of changes from contributors into one master.
Wed Oct 05, 2011 4:25 am Post
In total there are 3 users online :: 0 registered, 0 hidden and 3 guests (based on users active over the past 5 minutes)
Most users ever online was 1048 on Mon Feb 06, 2012 9:07 pm
Users browsing this forum: No registered users and 3 guests