When you go to File > Backup To, choose the location you want to save to. The next time you go to File > Backup To, that location will be remembered and selected by default.
All the best,
Keith
Does that location apply to auto save? And there is still no periodic backup feature right?
Auto-save saves to the project location, so no - it wouldn’t make any sense to have the backup location suddenly change the project location. And no, there is “still” no periodic backup; that’s coming in 2.0, most likely.
Sweet, thanks. I thought perhaps the SVN feature zipped the file and that it used the backup folder. I know it was a stretch. Thanks for the info.
No, I’m afraid not. 2.0 will definitely allow for zipped backups on open and close, and will also provide periodic backups if I can get it so that it doesn’t interrupt the workflow, though.
All the best,
Keith
Well as for the original question, let me add my vote for the evernote integration. By far the best for my own workflow would be via the evernote api (as is done in curio), so I could keep a reference copy of clipped notes etc in one place (in the evernote service), accessible across all projects etc.
Then for each writing project Scrivener could make local copies and keep them in the packages. In the best world they’d also be synchronized, but I’d be happy to start with at least importing!
Thanks for listening, and keep up the good work.
Oooh, sorry for hijacking the thread! I agree with the ideas about integrating with the Evernote API. Those guys are really great and very easy to work with. I’m sure they’d love to provide any help with the integration.
As I said before, Evernote integration is a nice idea, but I doubt it will be coming any time soon. The list for 2.0 is already intimidating. 
All the best,
Keith
Another vote for Evernote support. Seems like the best way to get scraps of writing from the iPhone into Scrivener.
Rather than Evernote support (or Google Docs, or whatever external site people are flocking to next year) I would like to see robust Applescript support. Evernote already has good Applescript support. Provide the facilities for the users who are interested in Evernote to build the importer.
I look at the example of BibDesk. The BibDesk developers have focused all their energies on building the core functionality of the app., and making as much of that as possible accessible through Applescript. Users have put together importers/exporters to hook BibDesk up to at least a dozen web sites and external programs.
Everyone is going to have different integration / import/export / backup / synchronization needs. IMHO Scrivener shouldn’t try to cater for specific solutions, but provide a general set of tools that can be harnessed by users to suit their particular workflow / configuration.
AppleScript is on the list for 2.0, and definitely a much higher priority than looking at the Evernote API, don’t worry. Whether it will make the cut for 2.0, based on time constraints and other things left to do, I’m not sure, but AppleScript is definitely something I want to add support for.
All the best,
Keith
Just want to add my support for this suggestion. I’ve been looking for a similar solution to jot story notes and ideas onto my iphone and move them simply into scrivener, my new best friend. Please give this serious consideration. Thanks!
As I have already said, it’s on the list for investigation but I very much doubt it will come in 2.0, given the enormous amount left to do.
Thanks and all the best,
Keith