A poor man's app updater
Brian Milby
brian at milby7.com
Fri Aug 3 20:48:11 EDT 2018
/Library is going to have the same permission issue, but
/Users/username/Library... would be fine.
The down side is that the user can accidentally or intentionally mess with
stuff stored there more easily that something built into the app or stored
in the Applications/Program Files directories (although the Finder does
hide the Library folder in the go menu unless to hold down the option
key). If it is more data related, then I think it is a great option. For
code updates, I'll let others more experienced comment.
Brian
On Fri, Aug 3, 2018 at 7:29 PM, Peter Bogdanoff via use-livecode <
use-livecode at lists.runrev.com> 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 at 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 at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
More information about the use-livecode
mailing list