Collaboration

[devinganger]

@JackSchaeffer

Once again, you go on the offensive to attack someone with a different POV

You have a fairly low threshold for what “the offensive” and an “attack” consist of, my friend. I assure you that you are reading far more heat into what I wrote than what I put there.

[JackSchaeffer]

Devin,

I guess it’s the cumulative effect of all my unfortunate interactions with you. But now that Version 3 is released and everyone is celebrating, I don’t care anymore.

I’ll leave you to have the last word.

[kewms]

While I stand by my fundamental point, that people have been predicting the doom of Scrivener for fifteen years and it hasn’t happened yet, the sarcasm was unnecessary and I apologize.

Best wishes for all success in your writing, whatever tools you choose.

Katherine

[AnotherGuy]

@kewms

…
Your hypothetical “lock” would therefore also need to protect the Binder structure, and so we’re right back to only one person being able to access the project at a time.
…
Katherine

So, is it completely safe to keep a project in a shared DropBox folder as far as only one person is accessing it at a time? No filesystem related metadata is kept locally?

[kewms]

@AnotherGuy

@kewms

…
Your hypothetical “lock” would therefore also need to protect the Binder structure, and so we’re right back to only one person being able to access the project at a time.
…
Katherine

So, is it completely safe to keep a project in a shared DropBox folder as far as only one person is accessing it at a time? No filesystem related metadata is kept locally?

A Scrivener project contains no information about where it was created or where it is “supposed” to be stored. You can freely transfer projects between computers. A shared Dropbox folder looks to Scrivener just like any other folder on the local computer: Scrivener doesn’t know (or care) that it’s a shared folder.

However, that doesn’t mean a shared folder is “completely safe.” Whenever a project is shared between devices, it’s possible for a conflict to occur if changes on device A are not synchronized back to device B. It’s also possible for some mechanism outside of Scrivener to damage the project: if a person with access to the shared folder simply deletes the entire project, there’s nothing Scrivener can do about it. Always have backups, and read this article on best practices to reduce the risk of synchronization errors:
scrivener.tenderapp.com/help/kb … c-services

Katherine

[JackSchaeffer]

Katherine,

Thank you. And for your help to me directly in the past.

I for one hope Scrivener is around for a long, long time. I purchased my upgrade yesterday to Win 3. I have a project that Scrivener is perfect for.

All the best to the Scrivener team.

Jack

[pigfender]

@devinganger

KB has far more access… Is he perfect?

@jackschaeffer

If you truly think I was “berating” KB (who I don’t know and have never heard of until you invoked his name)

Ah… this is a common misunderstanding. “KB” isn’t a real person, but a naming convention in tech / support circles. It stands for “Knowledge Base” and usually refers to a database of guidance and info sheets that support staff (and sometimes users) can refer to in order to get answers to both common and tricky questions. Because the original Scrivener Knowledge Base included the documents detailing the application design philosophy and architecture, “asking KB” became support staff code for looking up reasons why something couldn’t be done within the Scrivener paradigm.

The idea got more confused when, just before the LL forums migrated over to this site, AmberV programmed a forum bot to answer questions based on that Knowledge Base and called it KB. You’ll see it in early forum posts when people tried to personify KB by calling it “Kevin” and KB resisting (even including a specific request not to be called Kevin in its autosignature at one point).

I think AmberV has upgraded the programming several times since then, and now the bot is pretty realistic, and much more comfortable with being anthropomorphised - although “he” still doesn’t like being called Kevin.

It’s worth noting that I think several people have held the title “AmberV” over the years, so it’s not entirely clear how much the current post holder is still involved in the upkeep of KB’s code, but if he is (the current post holder is a young European male, I believe - LL doesn’t tend to broadcast this stuff) he should take a bow because the KB bot is one of the best I’ve interacted with and almost seems self-aware at this version.

[AnotherGuy]

@kewms

… and read this article on best practices to reduce the risk of synchronization errors:
scrivener.tenderapp.com/help/kb … c-services

Katherine

Thank you.

[creactiv]

@kewms

@creactiv

I was only asking for a locking mechanism, telling me, someone is using the document in the first place, so i dont crash my mates work. Second i was asking for being able to add content to the document in a secluded area, given, that i cannot work on the document parts another person is working on. Lets say, mate 1 opened entire document and i am working on a new chapter, this would be merged, as soon as both of us close the software.

Have you tried the Scrivener 3 beta? Scrivener 3 accomplishes this with the Import and Merge feature: both collaborators work independently, then the owner of the “master” version merges changes back in.

Katherine

I have to admit i didn’t try 3 Beta, because i was waiting for V3 release. Which came in the other day, and i got it today. So i will start fiddling a bit with that and figuring out about this mport and merge feature.

Will keep you posted

Thanks all of you, and i didn’t realize this would raise tension as it did, which wasn’t my intention at all.

And thank you Katherine to get back on this one… I will give it a try on Nextcloud to figure out.

Btw, i am writing manuals as well as translating fiction; so i am somehow in both worlds. My workflow would be to do the rough writing in Scrivener and put together what it needs and doing the finetuning in Papyrus.

Let’'s see, whether this will really work, while working on different devices.

Best