Accessing/Using the rest of my Dropbox?
It appears that Editorial is limited in its Dropbox access to a single defined folder and its children. I'd rather edit my files in the "proper" places in Dropbox because I access those files with many different applications and machines. Is there a way to do this that I am missing (if not, are there any plans to allow Editorial to access more of Dropbox)? Thanks!
In editorial's settings, set the sync folder to /, then you can see all of dropbox in editorial.
Can we please get the 'sync folder' setting in Pythonista too? When I do Dropbox Sync in Pythonista, I am always getting images, movies, books that I do not want downloaded into Pythonista.
Pythonista doesn't have Dropbox sync out-of-the-box, so what's downloaded depends on whatever script you may be using for this.
I'm worried about synch collisions if Editorial has access to my entire Dropbox.
There's no button to do a manual save in Editorial. Does this mean it's automatically saving as I edit? If so, does it save frequently enough to prevent synching collisions if I suddenly shut off my ipad and later edit the same document on another computer and then come back to Editorial?
What's best practice on this?
I personally prefer to keep Editorial contained in the default Dropbox setting, along with the children folders I've created within it - it works for my workflows for the most part, but that's just me. but I would like to be able to add specific folders, like for instance the folders I use for school, but without having all the folder present. It'd be nice to be able to add specific Dropbox folders similar to the way 1Writer handles DB folders.
+1 for the_buch's suggestion. I like the way 1Writer handel folders, too.
+1 as well. I have two main use cases: Blog post drafts and meeting / conference session notes. They belong in different places in DropBox.
Just to note that I have Editorial set to sync my entire Dropbox account (i.e. the sync folder is '/'). It syncs over 700 .md and .txt files fine. I've found Editorial to be very robust in this way, and never had conflicts, unless I really was editing a Dropbox file in both Editorial and on a PC.
One really neat thing I've found is that when you open a file in Editorial, it loads and seems to do a quick background check to see if the local copy of the file is out-of-date. If so, it gets-and-loads the latest version, and displays a little message that the file was updated. This works really well. My experience of many other iPad Dropbox Markdown editors is that this would cause a conflict.