0
iCloud Nested folders
Hello,
Textastic is a great app and I love using it. Now with the recent addition of iCloud support there is a seamless syncing of files which I am a fan of. I don't even have to push the files myself! The only downside to putting things on iCloud is the inability to make a folder within a folder. I'm guessing that this is a limitation of iCloud, but my organization of files would greatly benefit with even just one more layer of nested folders when using iCloud. I don't work on any large projects, so I can just make numerous top level folders if I really want to continue using the built-in iCloud support. Though is there a possibility of this being implemented?
Keep up the great work.
Thanks,
Josh
Customer support service by UserEcho
Yes, this is a limitation of iCloud. While I developed the iCloud functionality, I actually used a support ticked and asked Apple Worldwide Developer Technical Support. Here is their answer:
Two solutions, one relying on the fact that Apple is lying in this instance.
First, Textastic could support "bundled projects", this would allow storage and management (from within Textastic) of an entire tree of files represented as one "bundle" file on iCloud, or even locally. This would be neat.
Second, you absolutely can create folders in iCloud. I use them in iA Writer all the time! Here's an example of "folders" working in Textastic:
You create them by saving two different files, then simply dragging the second on top of the first. Bam, instant folder.
Errm... of course you can create *one level* of folders. The problem is that the open panel doesn't support subfolders. That's a decision Apple made. The underlying technology does in fact support subfolders (you can create subfolders in the Mobile Documents folder in Finder), but that functionality isn't exposed in the open panel.
They did say this in their answer: "NSOpenPanel does not offer any hooks to open up the iCloud account to navigate any further than one folder deep".
Indeed; #2 above is merely a hack while we wait for #1 to get implemented. ;P *nudge nudge*