Sat Jul 23, 2016 12:28 pm Post
Sat Jul 23, 2016 1:14 pm Post
Sat Jul 23, 2016 3:49 pm Post
Thu Oct 06, 2016 6:32 pm Post
Adopting iCloud document storage makes your app’s documents available on all of a user’s devices. A document (based on the UIDocument class in iOS or the NSDocument class in OS X) is an assemblage of related data that can be written to disk as a single file or as a file package. A file package, in turn, is a directory presented to the user as a single file and made accessible to your app through an NSFileWrapper object.
Thu Oct 06, 2016 7:24 pm Post
Fri Oct 07, 2016 2:23 pm Post
KB wrote:iWork doesn't save package files - it saves archives (zipped-up packages). It hasn't saved package files for several years now.
So yes, Pages does have a zip archive in its documents, but the document is still a package.A package is any directory that the Finder presents to the user as if it were a single file.
Fri Oct 07, 2016 2:58 pm Post
Red Claw wrote:So yes, Pages does have a zip archive in its documents, but the document is still a package.
A package is any directory that the Finder presents to the user as if it were a single file.
With this in mind, how would Scrivener Projects be handled? Could users run into the potential problems listed with iCloud and have a Scrivener project become unusable and corrupt?
Red Claw wrote:Remember, this in only a feature request, not a demand, and at this point is nothing more than an academic debate. Everyone on the Scrivener team has done an absolutely fantastic job creating this app. Keep up the good work.
Fri Oct 07, 2016 5:52 pm Post
KB wrote:The key word is "directory" - this does *not* include zip files, which are not directories (even though they may compress and contain directories) but are technically single files, and not file packages (in Apple's terminology). Pages and iWork do not save their files as packages, but as zip files, and a zip file is *not* a file package. A file package is just a regular folder of files that macOS presents in the Finder *as if* it were a single file, because an app is registered with the system that recognises the extension and tells macOS to treat it as a single file. If you move a .scriv file to a Windows machine or to any Mac that does not have Scrivener installed, it will appear as a regular file in the Finder. The same is not true of a .pages file.
You can test this for yourself by Ctrl-clicking on a file in the Finder. Any file that shows the "Show Package Contents" menu item in the contextual menu when you do this is a package file (this allows you to see inside the package); any file that does not show this option is not. Try this on a .scriv file and a .pages file, and you will clearly see that Pages files are not packages where Scrivener is.
KB wrote:Oh, I hope I'm not coming across in any way defensive.
Fri Oct 07, 2016 6:04 pm Post
kewms wrote:Um, Red Claw, are you really arguing with the developer of Scrivener about what his own software needs to function properly?
Fri Oct 07, 2016 10:05 pm Post
Sat Oct 08, 2016 3:29 am Post
AmberV wrote:Hmm, I’m not sure if having to remove the document from iCloud and then accessing an advanced optional feature to decompress the package is a good argument for packages working with iCloud.
If you explode the .pages archive into a folder of files, can you drag it back into iCloud and use it normally, syncing with an iPad, then return to the computer and find it is still a package? I don’t have iCloud myself, so I can’t test that, but I can explode a .pages file, fire it off to my phone with AirDrop, open it in Pages, edit it and send it back—and I get a .zip file, not a package.
At any rate, the principle argument is whether or not it is easy or feasible for third-party developers to use package technology with iCloud technology. Even if Pages does turn out to do that just fine and you get a package after a full round-trip cycle, it doesn’t prove much. Apple breaks all manner of rules that they set upon others. They use all kinds of technology nobody else has legitimate access to.
I mean after all, look at Pages and compare that text engine with the dregs they have everyone else using.
Sat Oct 08, 2016 8:12 am Post
Sat Oct 08, 2016 11:03 am Post
Red Claw wrote:So I can right-click on a Pages document in the Finder and "Show Package Contents", meaning that it is a package.KB wrote:Oh, I hope I'm not coming across in any way defensive.
Not at all. I think this is the whole point of a discussion forum. So people can have an insightful conversation.
In total there are 4 users online :: 0 registered, 0 hidden and 4 guests (based on users active over the past 5 minutes)
Most users ever online was 1048 on Mon Feb 06, 2012 9:07 pm
Users browsing this forum: No registered users and 4 guests