According to several recent posts I’ve been reading, the “Documents” directory is no longer supposed to be where we write out our “options” files. The reason being that users now have access to these files to delete, overwrite, modify, etc.
Quoting from: http://www.tuaw.com/2010/04/25/voices-that-matter-iphone-five-iphone-app-design-mistakes/
“Its time for the Documents folder to be used the way it is meant to be, the Apple way. Application support files belong in the Library folder, not in the Documents folder. The Documents folder is meant for Documents, which can be created, read, or edited by your application. All materials that support your application that are not user documents belong in the Library, preferably in an Application Support folder that you create yourself.
Solution: Keep your files in the Library folder. Surrender the Documents folder to the user.”
This seems like pretty good advice… the question is… where does this exist within the scope of Corona?
I see we have the following available:
• system.DocumentsDirectory should be used for files that need to persist between application sessions.
• system.TemporaryDirectory is a temporary directory. Files written to this directory are not guaranteed to exist in subsequent application sessions. They may or may not exist.
• system.ResourceDirectory is the directory where all application assets exist. Note: you should never create, modify, or add files to this directory (see Beware Security Violations).
ResourceDirectory is apparently a no-no… and TemporaryDirectory is… well… temporary.
So… is this a new feature request?
Scott [import]uid: 5659 topic_id: 897 reply_id: 300897[/import]