On Android, "documents" is sandboxed with the app, so isn't accessible
unless the device is rooted.
On 8/3/18 8:59 PM, Brian Milby via use-livecode wrote:
Yes, specialFolderPath would be good to use. On a desktop, I'm not sure
that I'd want non-user facing data stored in the documents location unless
you configure it to be hidden. Windows and Mac both have "support" folders
defined. "library" would be the place on iOS. Android doesn't have one
that makes sense off hand (other than "documents"). Linux doesn't have one
specified either, but you have access to the entire user's home directory
("home").
On Fri, Aug 3, 2018 at 8:05 PM, Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:
With the increasing use of sandboxing on Operating Systems (i.e. very
limited access on iOS and Android that will eventually be included in
desktop OSes), I might suggest using specialFolderPath("documents") and
creating a directory structure in there, say of the form
<companyName>/<appname>/ and whatever else you need. Documents is
becoming the one and only place where a user has guaranteed permissions
to access the contents for both read and write.
On 8/3/2018 8:29 PM, Peter Bogdanoff via use-livecode wrote:
So, to store and access LC stacks and other files used by myApp that
must be periodically updated, does it make sense to put them into
macOS—Library/Application Support/myApp
Win—user/AppData/myApp
rather than in Applications or Program Files?
Are there any restrictions or downside to this?
Peter
On Aug 3, 2018, at 5:14 AM, Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:
On 8/3/2018 2:32 AM, Peter Bogdanoff via use-livecode wrote:
Hi,
To raise the issue again of updating Mac and Windows apps, I’m
referencing this thread between Graham and Jacqueline...
Can existing files in the user’s application directory be
saved/modified/replaced by my application?
The accurate answer is that it all depends upon the permissions of the
account running the software. Typically for most personal or home
computers, the user has administrative privs, but that is increasingly
not the case on university or company owned computers. On these, they
may not have permission to alter files in the Program Files (Win) or
Applications (OSX) folders.
In some cases, again depending on OS and permissions, you can alter the
folders contents directly. In others you application must launch a
process (another app) with elevated privs, where the OS asks the user
for permissions for the elevated privs, and then that app (if allowed)
can make changes.
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode