[Req] iCloud for doc sync
theoriginalbudman last edited by
brianryer hit it on the nose..
brianryer last edited by
Good article on this topic recently appeared on MacStories
I guess what we're asking for is a file-picker implementation, not that everything else isn't already pretty flipping amazing, cuz it is.
Dann239 last edited by
I would like the developers input on this but I believe this still falls under the uncompiled code category. The reason we are stuck with a Dropbox sync script is because Apple didn't like the idea of syncing uncompiled code. I think Codea suffers from a similar disability?! A better sync option is much needed. I've resorted to archiving my script library and using Dropbox sync script to send over a single file as it struggled with folders.
TutorialDoctor last edited by
A few days ago. I found a script in the pytniosta forums that allow you to archive documents to a zip file. I modified it as an Editorial custom action. If you use "Documents by Readle" you might be able to save the file there (I have to check this out first), and from there you could sync.
But for local backups (which is very useful) it is still cool.
Use the File Bowser workflow I uploaded to open the zip in other apps.
ljbo last edited by
+1 for iCloud Drive support
StrugglingWriter last edited by
Adding my vote for iCloud Drive support. :)
nicolasharnois last edited by
And another +1 for iCloud Drive support! (the kind of implementation that would present an Editorial application folder in Finder on the Mac)
assistent last edited by
Hi, I just registered to add another vote for iCloud Drive integration. So... +1 :-)
ccc last edited by ccc
Apple's guidelines do not allow an applications that can run code to download code from iCloud.
See https://developer.apple.com/terms/ for the App Store Guideline and iOS Developer Guidelines
omz last edited by omz
@ccc This is about Editorial if I'm not mistaken, i.e. plain text files... Regarding Pythonista, you're right of course.
Webmaster4o last edited by
So, workflows could not be synced.
assistent last edited by
Yes, it would probably exclude workflows. Personally, I wouldn't care because I use Editorial almost exclusively to write text with Markdown. I don't want to start another political debate about Dropbox. I do however argue that Editorial needs to implement the Apple standard for cloud syncing if it aims to be about total ios integration.
An Editorial update with icloud drive integration would make this user very happy :-)
johnwhitley last edited by
Having the iCloud picker would be great, as that would allow integration with the wonderful app Working Copy, a Git client for iOS that includes an iCloud document picker.
GelatsX last edited by
One more vote for iCloud Drive support! It'd be so great.
batmanx last edited by
LennyAbramov last edited by
Upvote for icloud support :)
rbnfrngpls last edited by
Please add this!
Other Markdown editors already support this.
peterdubbelman last edited by
I also look forward to the day Editorial files can be stored in iCloud Drive! It will make workflows so much smoother! iCloud Drive is standard by now and most other editors support it. I love Editorial for its superior design and flexibility, but not having iCloud Drive really is a pain for anyone having a reason not to use Dropbox.
mbarritt last edited by
+1 for iCloud and iOS Files app integration - open from in particular, I would appreciate the option (as now works with Byword, for example) to open a .md file from the iOS files app in Editorial (a file stored in the iCloud Drive) edit it, and have it remain in the iOS Files/iCloud space.
silverkors last edited by
+1 for iCloud Drive support. To just switch out Dropbox for iCloud sync. That would be great!