Actually, you can have Scrivener and Timeline open at the same time. But it's wise to close Scrivener when you're finished getting the info you want.
Yes, you only need to close Scrivener if you are actively syncing. If you don't open the binder in AT2, you can keep both programs open as much as you want.
Thanks folks, but as you can imagine, the distinction of "actively syncing" vs. "not actively syncing" is one mistake away -- I'd be nervous taking the chance with a large novel. Even if it were entirely safe, still far less convenient than being able to see the text in-place. Any chance of this feature getting on the roadmap?
partnerinflight - It's really pretty simple. As razyr suggests, just don't open the Scrivener binder until/unless you want to sync.
Heya, PIF. Yes, there's really no chance of accidentally squashing information in either direction. First, you have to explicitly open the Scrivener binder from AT2 and it will alert you if the binder is open in another program. Second, before AT2 will sync your data, it will show you what the data looks like in each source (AT2 and binder) and let you decide field by field, object by object whether you want to sync and which source you want to sync from. You could have a single object where you elect to perhaps update one field in the binder from AT2 and another field where you update AT2 from the binder. What you're asking for isn't really possible. Scrivener expects to have exclusive access to the binder. Your project in Scrivener is stored in multiple files. Those files are not being continuously read. Nor are they continuously being written to. There's simply no way for Scrivener to know if a 3rd party program has changed the content of a file. So potentially, you're editing an event in Scrivener, so now Scrivener has a current view of the "data". Then you open AT2, make a change and write to the binder. Scrivener doesn't know. Now you make a save in Scrivener, which naively overwrites your update from AT2. It's not like Scrivener is using a database where records could be locked, marked as dirty for write, etc... The Scrivener/AT2 sync isn't perfect, but the least of your concerns should be whether your data is at risk. It's a very clean and well-written synchronization process. Additionally, both programs do an excellent job of creating backups, even if you did manage to somehow clobber something.
Thanks razyr. What I'm asking about is functionality inside AT that would give me the preview of the text. That way I could keep Scrivener closed. But given your points above, I could make do with having the two apps side by side. Thanks!
Hi, Unfortunately we are unable to have both Scrivener and Aeon Timeline open at the same time when syncing due to limitations with Scrivener (it can't have two copies of the same file open at once), so there is nothing we can do about it at this point in time. Jess
Hi Jess. Sorry, I don't think I'm communicating the request correctly. I'm NOT asking to have both open at the same time. That's actually something I want to avoid needing to do. Instead, I'm asking to add the ability to view a Scrivener document (scene, chapter, etc) inside AT2 directly. Does that make sense?
Hi, This is something I have thought about adding in the past, but it is a little bit complicated. Internally, Scrivener stores individual RTF files for each document in the Binder. In theory, I could load those up and show the text. Unfortunately, Aeon doesn't have anything to support rich text out of the box. On Mac, one option would be to allow the user to Quicklook the RTF file, which would be very quick and easy to implement. Unfortunately, Quicklook adds an "Open" button at the top, which would then open the text file in an editor like TextEdit. This isn't a good option, as Scrivener doesn't like having those files edited behind its back. And it also doesn't account for Windows. So instead we would probably have to create something that can read and display the Rich text files... which is certainly not impossible, but there is a fair bit more work involved. Still, I will add it to the development list to consider in a future version. Thanks, Matt