Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

fyi, to anyone else coming to thie thread, you can't use revCopyFolder or
revCopyFile to move your bundle stacks/files to the documents folder b/c
both commands require a shell, and ios doesn't have shell support.

On Sat, Mar 2, 2024 at 1:07 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Thanks for checking, now I don't have to change anything. Android also has
> both a sandboxed documents folder and a public one.
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On March 2, 2024 11:55:52 AM Mike Kerner via use-livecode
>  wrote:
>
> > looks like specialfolderpath("documents") is sandboxed, after all.
> > apparently there is another Documents folder, that lc isn't accessing,
> that
> > is not.
> >
> > On Fri, Mar 1, 2024 at 6:39 PM J. Landman Gay via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> >> Let me know if you find out. I'm still running in the before times.
> >>
> >> --
> >> Jacqueline Landman Gay | jac...@hyperactivesw.com
> >> HyperActive Software | http://www.hyperactivesw.com
> >> On March 1, 2024 12:25:21 PM Mike Kerner via use-livecode
> >>  wrote:
> >>
> >> > the latest pieces that i found on the topic said that files can access
> >> the
> >> > documents folder (but not library), and that it is available by other
> >> > means, without jailbreaking.
> >> > thus, i need to screw around with this, some more.
> >> > if it's unavailable, then great, no need for library.
> >> > in The Before Times, documents was isolated, but i thought that
> changed.
> >> >
> >> > On Fri, Mar 1, 2024 at 1:10 PM J. Landman Gay via use-livecode <
> >> > use-livecode@lists.runrev.com> wrote:
> >> >
> >> >> A quick test would be to see if Files can access the private
> documents
> >> of
> >> >> any installed app. I could try it if I didn't have to steal my
> husband's
> >> >> phone, which is tricky business.
> >> >>
> >> >> --
> >> >> Jacqueline Landman Gay | jac...@hyperactivesw.com
> >> >> HyperActive Software | http://www.hyperactivesw.com
> >> >> On March 1, 2024 11:40:09 AM Mike Kerner via use-livecode
> >> >>  wrote:
> >> >>
> >> >> > i'm going to have to mess with this, some more. i didn't think
> >> documents
> >> >> is
> >> >> > sandboxed.
> >> >> >
> >> >> >
> >> >> > On Fri, Mar 1, 2024 at 11:49 AM Bob Sneidar via use-livecode <
> >> >> > use-livecode@lists.runrev.com> wrote:
> >> >> >
> >> >> >> They should stop calling it a Sandbox then. It’s the entire beach!
> >> LOL!
> >> >> >>
> >> >> >> Bob S
> >> >> >>
> >> >> >>
> >> >> >> On Mar 1, 2024, at 8:45 AM, J. Landman Gay via use-livecode <
> >> >> >> use-livecode@lists.runrev.com> wrote:
> >> >> >>
> >> >> >> Right. In spite of Android's "external documents" option, which I
> >> >> needed,
> >> >> >> it's still in the sandbox.
> >> >> >>
> >> >> >> --
> >> >> >> Jacqueline Landman Gay | jac...@hyperactivesw.com >> >> >> jac...@hyperactivesw.com>
> >> >> >> HyperActive Software | http://www.hyperactivesw.com<
> >> >> >> http://www.hyperactivesw.com/>
> >> >> >> On March 1, 2024 10:42:04 AM Bob Sneidar via use-livecode <
> >> >> >> use-livecode@lists.runrev.com> wrote:
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> ___
> >> >> >> 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
> >> >> >>
> >> >> >
> >> >> >
> >> >> > --
> >> >> > On the first day, God created the heavens and the Earth
> >> >> > On the second day, God created the oceans.
> >> >> > On the third day, God put the animals on hold for a few hours,
> >> >> >   and did a little diving.
> >> >> > And God said, "This is good."
> >> >> > ___
> >> >> > 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
> >> >>
> >> >
> >> >
> >> > --
> >> > On the first day, God created the heavens and the Earth
> >> > On the second day, God created the oceans.
> >> > On the third day, God put the animals on hold for a few hours,
> >> >   and did a little diving.
> >> > And God said, "This is good."
> >> > ___
> >> > use-livecode mailing list
> >> > use-livecode@lists.runrev.com
> >> > Please visit this url to subscribe, unsubscribe and manage your
> >> > subscription preferences:

Re: sideloading updates to mobile

[J. Landman Gay via use-livecode]

Thanks for checking, now I don't have to change anything. Android also has 
both a sandboxed documents folder and a public one.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On March 2, 2024 11:55:52 AM Mike Kerner via use-livecode 
 wrote:



looks like specialfolderpath("documents") is sandboxed, after all.
apparently there is another Documents folder, that lc isn't accessing, that
is not.

On Fri, Mar 1, 2024 at 6:39 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:


Let me know if you find out. I'm still running in the before times.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On March 1, 2024 12:25:21 PM Mike Kerner via use-livecode
 wrote:

> the latest pieces that i found on the topic said that files can access
the
> documents folder (but not library), and that it is available by other
> means, without jailbreaking.
> thus, i need to screw around with this, some more.
> if it's unavailable, then great, no need for library.
> in The Before Times, documents was isolated, but i thought that changed.
>
> On Fri, Mar 1, 2024 at 1:10 PM J. Landman Gay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> A quick test would be to see if Files can access the private documents
of
>> any installed app. I could try it if I didn't have to steal my husband's
>> phone, which is tricky business.
>>
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On March 1, 2024 11:40:09 AM Mike Kerner via use-livecode
>>  wrote:
>>
>> > i'm going to have to mess with this, some more. i didn't think
documents
>> is
>> > sandboxed.
>> >
>> >
>> > On Fri, Mar 1, 2024 at 11:49 AM Bob Sneidar via use-livecode <
>> > use-livecode@lists.runrev.com> wrote:
>> >
>> >> They should stop calling it a Sandbox then. It’s the entire beach!
LOL!
>> >>
>> >> Bob S
>> >>
>> >>
>> >> On Mar 1, 2024, at 8:45 AM, J. Landman Gay via use-livecode <
>> >> use-livecode@lists.runrev.com> wrote:
>> >>
>> >> Right. In spite of Android's "external documents" option, which I
>> needed,
>> >> it's still in the sandbox.
>> >>
>> >> --
>> >> Jacqueline Landman Gay | jac...@hyperactivesw.com> >> jac...@hyperactivesw.com>
>> >> HyperActive Software | http://www.hyperactivesw.com<
>> >> http://www.hyperactivesw.com/>
>> >> On March 1, 2024 10:42:04 AM Bob Sneidar via use-livecode <
>> >> use-livecode@lists.runrev.com> wrote:
>> >>
>> >>
>> >>
>> >> ___
>> >> 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
>> >>
>> >
>> >
>> > --
>> > On the first day, God created the heavens and the Earth
>> > On the second day, God created the oceans.
>> > On the third day, God put the animals on hold for a few hours,
>> >   and did a little diving.
>> > And God said, "This is good."
>> > ___
>> > 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
>>
>
>
> --
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
>   and did a little diving.
> And God said, "This is good."
> ___
> 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




--
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
  and did a little diving.
And God said, "This is good."
___
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
Pl

Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

looks like specialfolderpath("documents") is sandboxed, after all.
apparently there is another Documents folder, that lc isn't accessing, that
is not.

On Fri, Mar 1, 2024 at 6:39 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Let me know if you find out. I'm still running in the before times.
>
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On March 1, 2024 12:25:21 PM Mike Kerner via use-livecode
>  wrote:
>
> > the latest pieces that i found on the topic said that files can access
> the
> > documents folder (but not library), and that it is available by other
> > means, without jailbreaking.
> > thus, i need to screw around with this, some more.
> > if it's unavailable, then great, no need for library.
> > in The Before Times, documents was isolated, but i thought that changed.
> >
> > On Fri, Mar 1, 2024 at 1:10 PM J. Landman Gay via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> >> A quick test would be to see if Files can access the private documents
> of
> >> any installed app. I could try it if I didn't have to steal my husband's
> >> phone, which is tricky business.
> >>
> >> --
> >> Jacqueline Landman Gay | jac...@hyperactivesw.com
> >> HyperActive Software | http://www.hyperactivesw.com
> >> On March 1, 2024 11:40:09 AM Mike Kerner via use-livecode
> >>  wrote:
> >>
> >> > i'm going to have to mess with this, some more. i didn't think
> documents
> >> is
> >> > sandboxed.
> >> >
> >> >
> >> > On Fri, Mar 1, 2024 at 11:49 AM Bob Sneidar via use-livecode <
> >> > use-livecode@lists.runrev.com> wrote:
> >> >
> >> >> They should stop calling it a Sandbox then. It’s the entire beach!
> LOL!
> >> >>
> >> >> Bob S
> >> >>
> >> >>
> >> >> On Mar 1, 2024, at 8:45 AM, J. Landman Gay via use-livecode <
> >> >> use-livecode@lists.runrev.com> wrote:
> >> >>
> >> >> Right. In spite of Android's "external documents" option, which I
> >> needed,
> >> >> it's still in the sandbox.
> >> >>
> >> >> --
> >> >> Jacqueline Landman Gay | jac...@hyperactivesw.com >> >> jac...@hyperactivesw.com>
> >> >> HyperActive Software | http://www.hyperactivesw.com<
> >> >> http://www.hyperactivesw.com/>
> >> >> On March 1, 2024 10:42:04 AM Bob Sneidar via use-livecode <
> >> >> use-livecode@lists.runrev.com> wrote:
> >> >>
> >> >>
> >> >>
> >> >> ___
> >> >> 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
> >> >>
> >> >
> >> >
> >> > --
> >> > On the first day, God created the heavens and the Earth
> >> > On the second day, God created the oceans.
> >> > On the third day, God put the animals on hold for a few hours,
> >> >   and did a little diving.
> >> > And God said, "This is good."
> >> > ___
> >> > 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
> >>
> >
> >
> > --
> > On the first day, God created the heavens and the Earth
> > On the second day, God created the oceans.
> > On the third day, God put the animals on hold for a few hours,
> >   and did a little diving.
> > And God said, "This is good."
> > ___
> > 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
>


-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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

Re: sideloading updates to mobile

[J. Landman Gay via use-livecode]

Let me know if you find out. I'm still running in the before times.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On March 1, 2024 12:25:21 PM Mike Kerner via use-livecode 
 wrote:



the latest pieces that i found on the topic said that files can access the
documents folder (but not library), and that it is available by other
means, without jailbreaking.
thus, i need to screw around with this, some more.
if it's unavailable, then great, no need for library.
in The Before Times, documents was isolated, but i thought that changed.

On Fri, Mar 1, 2024 at 1:10 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:


A quick test would be to see if Files can access the private documents of
any installed app. I could try it if I didn't have to steal my husband's
phone, which is tricky business.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On March 1, 2024 11:40:09 AM Mike Kerner via use-livecode
 wrote:

> i'm going to have to mess with this, some more. i didn't think documents
is
> sandboxed.
>
>
> On Fri, Mar 1, 2024 at 11:49 AM Bob Sneidar via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> They should stop calling it a Sandbox then. It’s the entire beach! LOL!
>>
>> Bob S
>>
>>
>> On Mar 1, 2024, at 8:45 AM, J. Landman Gay via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>
>> Right. In spite of Android's "external documents" option, which I
needed,
>> it's still in the sandbox.
>>
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com> jac...@hyperactivesw.com>
>> HyperActive Software | http://www.hyperactivesw.com<
>> http://www.hyperactivesw.com/>
>> On March 1, 2024 10:42:04 AM Bob Sneidar via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>
>>
>>
>> ___
>> 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
>>
>
>
> --
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
>   and did a little diving.
> And God said, "This is good."
> ___
> 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




--
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
  and did a little diving.
And God said, "This is good."
___
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

Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

the latest pieces that i found on the topic said that files can access the
documents folder (but not library), and that it is available by other
means, without jailbreaking.
thus, i need to screw around with this, some more.
if it's unavailable, then great, no need for library.
in The Before Times, documents was isolated, but i thought that changed.

On Fri, Mar 1, 2024 at 1:10 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> A quick test would be to see if Files can access the private documents of
> any installed app. I could try it if I didn't have to steal my husband's
> phone, which is tricky business.
>
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On March 1, 2024 11:40:09 AM Mike Kerner via use-livecode
>  wrote:
>
> > i'm going to have to mess with this, some more. i didn't think documents
> is
> > sandboxed.
> >
> >
> > On Fri, Mar 1, 2024 at 11:49 AM Bob Sneidar via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> >> They should stop calling it a Sandbox then. It’s the entire beach! LOL!
> >>
> >> Bob S
> >>
> >>
> >> On Mar 1, 2024, at 8:45 AM, J. Landman Gay via use-livecode <
> >> use-livecode@lists.runrev.com> wrote:
> >>
> >> Right. In spite of Android's "external documents" option, which I
> needed,
> >> it's still in the sandbox.
> >>
> >> --
> >> Jacqueline Landman Gay | jac...@hyperactivesw.com >> jac...@hyperactivesw.com>
> >> HyperActive Software | http://www.hyperactivesw.com<
> >> http://www.hyperactivesw.com/>
> >> On March 1, 2024 10:42:04 AM Bob Sneidar via use-livecode <
> >> use-livecode@lists.runrev.com> wrote:
> >>
> >>
> >>
> >> ___
> >> 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
> >>
> >
> >
> > --
> > On the first day, God created the heavens and the Earth
> > On the second day, God created the oceans.
> > On the third day, God put the animals on hold for a few hours,
> >   and did a little diving.
> > And God said, "This is good."
> > ___
> > 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
>


-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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

Re: sideloading updates to mobile

[J. Landman Gay via use-livecode]

A quick test would be to see if Files can access the private documents of 
any installed app. I could try it if I didn't have to steal my husband's 
phone, which is tricky business.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On March 1, 2024 11:40:09 AM Mike Kerner via use-livecode 
 wrote:



i'm going to have to mess with this, some more. i didn't think documents is
sandboxed.


On Fri, Mar 1, 2024 at 11:49 AM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:


They should stop calling it a Sandbox then. It’s the entire beach! LOL!

Bob S


On Mar 1, 2024, at 8:45 AM, J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

Right. In spite of Android's "external documents" option, which I needed,
it's still in the sandbox.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com<
http://www.hyperactivesw.com/>
On March 1, 2024 10:42:04 AM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:



___
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




--
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
  and did a little diving.
And God said, "This is good."
___
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

Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

i'm going to have to mess with this, some more. i didn't think documents is
sandboxed.


On Fri, Mar 1, 2024 at 11:49 AM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:

> They should stop calling it a Sandbox then. It’s the entire beach! LOL!
>
> Bob S
>
>
> On Mar 1, 2024, at 8:45 AM, J. Landman Gay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> Right. In spite of Android's "external documents" option, which I needed,
> it's still in the sandbox.
>
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com jac...@hyperactivesw.com>
> HyperActive Software | http://www.hyperactivesw.com<
> http://www.hyperactivesw.com/>
> On March 1, 2024 10:42:04 AM Bob Sneidar via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>
>
> ___
> 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
>


-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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

Re: sideloading updates to mobile

[J. Landman Gay via use-livecode]

But it's a private beach. No trespassing. Guards. Barbed wire.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On March 1, 2024 10:50:17 AM Bob Sneidar via use-livecode 
 wrote:



They should stop calling it a Sandbox then. It’s the entire beach! LOL!

Bob S


On Mar 1, 2024, at 8:45 AM, J. Landman Gay via use-livecode 
 wrote:


Right. In spite of Android's "external documents" option, which I needed, 
it's still in the sandbox.


--
Jacqueline Landman Gay | 
jac...@hyperactivesw.com
HyperActive Software | 
http://www.hyperactivesw.com
On March 1, 2024 10:42:04 AM Bob Sneidar via use-livecode 
 wrote:




___
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

Re: sideloading updates to mobile

[Bob Sneidar via use-livecode]

They should stop calling it a Sandbox then. It’s the entire beach! LOL!

Bob S


On Mar 1, 2024, at 8:45 AM, J. Landman Gay via use-livecode 
 wrote:

Right. In spite of Android's "external documents" option, which I needed, it's 
still in the sandbox.

--
Jacqueline Landman Gay | 
jac...@hyperactivesw.com
HyperActive Software | 
http://www.hyperactivesw.com
On March 1, 2024 10:42:04 AM Bob Sneidar via use-livecode 
 wrote:



___
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

Re: sideloading updates to mobile

[J. Landman Gay via use-livecode]

Right. In spite of Android's "external documents" option, which I needed, 
it's still in the sandbox.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On March 1, 2024 10:42:04 AM Bob Sneidar via use-livecode 
 wrote:



Hell that means EVERYTHING is sandboxed! I need to go buy a pail and shovel!

Bob S


On Mar 1, 2024, at 8:31 AM, J. Landman Gay via use-livecode 
 wrote:


Both library and documents are sandboxed, I think all the listed folders 
are. I mostly use documents so that I have the same file paths on both iOS 
and Android since I generally need to build for both. But either one will work.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On March 1, 2024 10:08:15 AM Bob Sneidar via use-livecode 
 wrote:



Isn’t the Library sandboxed?

Bob S


On Feb 29, 2024, at 6:35 PM, Mike Kerner via use-livecode 
 wrote:


any reason to store in documents instead of in library?
it seems like there might be less of a chance of the user misusing the
Files app to break the app.

On Thu, Feb 29, 2024 at 5:32 PM Mike Kerner 
mailto:mikeker...@roadrunner.com>>

wrote:

ah. that's a better way of handling this. i was going to have the app
check the documents folder for updates, before loading a stack, but if i
keep the source stacks, there, it will work better.

On Thu, Feb 29, 2024 at 3:10 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

You can't add or change anything inside the app bundle so downloaded
files
have to go in specialFolderPath("documents"). Copy the originals from the
resources folder to the documents folder on first launch so you always
have
a known file path location. Any file in documents will be overwritten
with
the new download if the file name is the same.


___
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

Re: sideloading updates to mobile

[Bob Sneidar via use-livecode]

Hell that means EVERYTHING is sandboxed! I need to go buy a pail and shovel! 

Bob S


> On Mar 1, 2024, at 8:31 AM, J. Landman Gay via use-livecode 
>  wrote:
> 
> Both library and documents are sandboxed, I think all the listed folders are. 
> I mostly use documents so that I have the same file paths on both iOS and 
> Android since I generally need to build for both. But either one will work.
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On March 1, 2024 10:08:15 AM Bob Sneidar via use-livecode 
>  wrote:
> 
>> Isn’t the Library sandboxed?
>> 
>> Bob S
>> 
>> 
>> On Feb 29, 2024, at 6:35 PM, Mike Kerner via use-livecode 
>>  wrote:
>> 
>> any reason to store in documents instead of in library?
>> it seems like there might be less of a chance of the user misusing the
>> Files app to break the app.
>> 
>> On Thu, Feb 29, 2024 at 5:32 PM Mike Kerner 
>> mailto:mikeker...@roadrunner.com>>
>> wrote:
>> 
>> ah. that's a better way of handling this. i was going to have the app
>> check the documents folder for updates, before loading a stack, but if i
>> keep the source stacks, there, it will work better.
>> 
>> On Thu, Feb 29, 2024 at 3:10 PM J. Landman Gay via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>> You can't add or change anything inside the app bundle so downloaded
>> files
>> have to go in specialFolderPath("documents"). Copy the originals from the
>> resources folder to the documents folder on first launch so you always
>> have
>> a known file path location. Any file in documents will be overwritten
>> with
>> the new download if the file name is the same.
>> 
>> 
>> ___
>> 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

Re: sideloading updates to mobile

[J. Landman Gay via use-livecode]

Both library and documents are sandboxed, I think all the listed folders 
are. I mostly use documents so that I have the same file paths on both iOS 
and Android since I generally need to build for both. But either one will work.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On March 1, 2024 10:08:15 AM Bob Sneidar via use-livecode 
 wrote:



Isn’t the Library sandboxed?

Bob S


On Feb 29, 2024, at 6:35 PM, Mike Kerner via use-livecode 
 wrote:


any reason to store in documents instead of in library?
it seems like there might be less of a chance of the user misusing the
Files app to break the app.

On Thu, Feb 29, 2024 at 5:32 PM Mike Kerner 
mailto:mikeker...@roadrunner.com>>

wrote:

ah. that's a better way of handling this. i was going to have the app
check the documents folder for updates, before loading a stack, but if i
keep the source stacks, there, it will work better.

On Thu, Feb 29, 2024 at 3:10 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

You can't add or change anything inside the app bundle so downloaded
files
have to go in specialFolderPath("documents"). Copy the originals from the
resources folder to the documents folder on first launch so you always
have
a known file path location. Any file in documents will be overwritten
with
the new download if the file name is the same.


___
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

Re: sideloading updates to mobile

[Bob Sneidar via use-livecode]

Isn’t the Library sandboxed?

Bob S


On Feb 29, 2024, at 6:35 PM, Mike Kerner via use-livecode 
 wrote:

any reason to store in documents instead of in library?
it seems like there might be less of a chance of the user misusing the
Files app to break the app.

On Thu, Feb 29, 2024 at 5:32 PM Mike Kerner 
mailto:mikeker...@roadrunner.com>>
wrote:

ah. that's a better way of handling this. i was going to have the app
check the documents folder for updates, before loading a stack, but if i
keep the source stacks, there, it will work better.

On Thu, Feb 29, 2024 at 3:10 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

You can't add or change anything inside the app bundle so downloaded
files
have to go in specialFolderPath("documents"). Copy the originals from the
resources folder to the documents folder on first launch so you always
have
a known file path location. Any file in documents will be overwritten
with
the new download if the file name is the same.


___
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

Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

any reason to store in documents instead of in library?
it seems like there might be less of a chance of the user misusing the
Files app to break the app.

On Thu, Feb 29, 2024 at 5:32 PM Mike Kerner 
wrote:

> ah. that's a better way of handling this. i was going to have the app
> check the documents folder for updates, before loading a stack, but if i
> keep the source stacks, there, it will work better.
>
> On Thu, Feb 29, 2024 at 3:10 PM J. Landman Gay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> You can't add or change anything inside the app bundle so downloaded
>> files
>> have to go in specialFolderPath("documents"). Copy the originals from the
>> resources folder to the documents folder on first launch so you always
>> have
>> a known file path location. Any file in documents will be overwritten
>> with
>> the new download if the file name is the same.
>>
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On February 29, 2024 7:31:28 AM Mike Kerner via use-livecode
>>  wrote:
>>
>> > i haven't tried deploying to a device, yet, so bear with me:
>> > when you load the updated stack/behavior/etc., are you saving it into
>> the
>> > app bundle, or elsewhere? on locked/single-app devices, persistence is
>> the
>> > thing (but i would imagine that it works the same on single-app devices
>> as
>> > it does for normal ones).
>> >
>> > On Wed, Feb 28, 2024 at 10:12 PM J. Landman Gay via use-livecode <
>> > use-livecode@lists.runrev.com> wrote:
>> >
>> >> "Revert this stack". That just means "reload from disk". Or you can
>> >> specify
>> >> a different stack.
>> >> --
>> >> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> >> HyperActive Software | http://www.hyperactivesw.com
>> >> On February 28, 2024 8:12:57 PM Mike Kerner via use-livecode
>> >>  wrote:
>> >>
>> >> > so, how do we force LC to reload the stack?
>> >> > i can force the script to reload, and replace it, but if i want to
>> reload
>> >> > the stack, do i have to close it, replace it, and then open it?
>> >> >
>> >> > On Wed, Feb 21, 2024 at 8:28 PM Mike Kerner <
>> mikeker...@roadrunner.com>
>> >> > wrote:
>> >> >
>> >> >> thanks, jlg. that's kind-of what i was thinking.
>> >> >>
>> >> >>
>> >> >> On Wed, Feb 21, 2024 at 4:58 PM J. Landman Gay via use-livecode <
>> >> >> use-livecode@lists.runrev.com> wrote:
>> >> >>
>> >> >>> I've done this for several mobile apps. As long as the updates only
>> >> >>> reside
>> >> >>> in the app's sandboxed container, even the App Store doesn't care.
>> >> >>>
>> >> >>> Basically, I put a short text file on the server listing the update
>> >> >>> version(s) of the file(s), one per line if they are all different.
>> >> Every
>> >> >>> stack in the app suite has a custom property named cVersion. If
>> >> necessary
>> >> >>> you can also add the download URL to the same line. On launch, the
>> app
>> >> >>> downloads and parses the text to see if the server version is
>> different
>> >> >>> from the installed one. If so, it uses "put URL  into
>> URL
>> >> >>> > >> >>> path>" to download and save the the updates to the mobile documents
>> >> >>> folder,
>> >> >>> overwriting the old ones.
>> >> >>>
>> >> >>> It's pretty simple, if I understand what you need correctly. I also
>> >> store
>> >> >>> other info in the the text file occasionally, such as a text string
>> >> >>> describing the updates so I can show an answer dialog if I want the
>> >> user
>> >> >>> to
>> >> >>> agree or decline the update (which will reappear on the next
>> launch if
>> >> >>> they
>> >> >>> decline.)
>> >> >>>
>> >> >>> Sample text file is usually something like this:
>> >> >>>
>> >> >>>Stack 1  https://www.domain.com/updates/stack1.livecode
>> >> >>>Stack 2  https://www.domain.com/updates/stack2.livecode
>> >> >>>..
>> >> >>>This update provides new functionality and bug fixes.
>> >> >>>
>> >> >>> If you don't want to scan each stack for its cVersion, you can
>> keep a
>> >> >>> text
>> >> >>> file in the mobile documents folder that lists the current
>> versions so
>> >> >>> you
>> >> >>> can easily compare that to the one on the server. After updating
>> the
>> >> >>> stacks, update the stored text file as well.
>> >> >>>
>> >> >>> If updates are mandatory, just skip the comparisons entirely and
>> >> >>> force-download the updates. If only some of the stacks should be
>> >> updated,
>> >> >>> omit the ones that don't need to be updated from the server file.
>> >> >>>
>> >> >>> --
>> >> >>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> >> >>> HyperActive Software | http://www.hyperactivesw.com
>> >> >>> On February 21, 2024 12:53:25 PM Mike Kerner via use-livecode
>> >> >>>  wrote:
>> >> >>>
>> >> >>> > right - no updating the engine + runtime in this scenario, just
>> the
>> >> >>> > stacks + scripts, and perhaps plugins.
>> >> >>> > we are going to continue to only privately distribute to our
>> >> corporate
>> >> 

Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

ah. that's a better way of handling this. i was going to have the app check
the documents folder for updates, before loading a stack, but if i keep the
source stacks, there, it will work better.

On Thu, Feb 29, 2024 at 3:10 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> You can't add or change anything inside the app bundle so downloaded files
> have to go in specialFolderPath("documents"). Copy the originals from the
> resources folder to the documents folder on first launch so you always
> have
> a known file path location. Any file in documents will be overwritten with
> the new download if the file name is the same.
>
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On February 29, 2024 7:31:28 AM Mike Kerner via use-livecode
>  wrote:
>
> > i haven't tried deploying to a device, yet, so bear with me:
> > when you load the updated stack/behavior/etc., are you saving it into the
> > app bundle, or elsewhere? on locked/single-app devices, persistence is
> the
> > thing (but i would imagine that it works the same on single-app devices
> as
> > it does for normal ones).
> >
> > On Wed, Feb 28, 2024 at 10:12 PM J. Landman Gay via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> >> "Revert this stack". That just means "reload from disk". Or you can
> >> specify
> >> a different stack.
> >> --
> >> Jacqueline Landman Gay | jac...@hyperactivesw.com
> >> HyperActive Software | http://www.hyperactivesw.com
> >> On February 28, 2024 8:12:57 PM Mike Kerner via use-livecode
> >>  wrote:
> >>
> >> > so, how do we force LC to reload the stack?
> >> > i can force the script to reload, and replace it, but if i want to
> reload
> >> > the stack, do i have to close it, replace it, and then open it?
> >> >
> >> > On Wed, Feb 21, 2024 at 8:28 PM Mike Kerner <
> mikeker...@roadrunner.com>
> >> > wrote:
> >> >
> >> >> thanks, jlg. that's kind-of what i was thinking.
> >> >>
> >> >>
> >> >> On Wed, Feb 21, 2024 at 4:58 PM J. Landman Gay via use-livecode <
> >> >> use-livecode@lists.runrev.com> wrote:
> >> >>
> >> >>> I've done this for several mobile apps. As long as the updates only
> >> >>> reside
> >> >>> in the app's sandboxed container, even the App Store doesn't care.
> >> >>>
> >> >>> Basically, I put a short text file on the server listing the update
> >> >>> version(s) of the file(s), one per line if they are all different.
> >> Every
> >> >>> stack in the app suite has a custom property named cVersion. If
> >> necessary
> >> >>> you can also add the download URL to the same line. On launch, the
> app
> >> >>> downloads and parses the text to see if the server version is
> different
> >> >>> from the installed one. If so, it uses "put URL  into
> URL
> >> >>>  >> >>> path>" to download and save the the updates to the mobile documents
> >> >>> folder,
> >> >>> overwriting the old ones.
> >> >>>
> >> >>> It's pretty simple, if I understand what you need correctly. I also
> >> store
> >> >>> other info in the the text file occasionally, such as a text string
> >> >>> describing the updates so I can show an answer dialog if I want the
> >> user
> >> >>> to
> >> >>> agree or decline the update (which will reappear on the next launch
> if
> >> >>> they
> >> >>> decline.)
> >> >>>
> >> >>> Sample text file is usually something like this:
> >> >>>
> >> >>>Stack 1  https://www.domain.com/updates/stack1.livecode
> >> >>>Stack 2  https://www.domain.com/updates/stack2.livecode
> >> >>>..
> >> >>>This update provides new functionality and bug fixes.
> >> >>>
> >> >>> If you don't want to scan each stack for its cVersion, you can keep
> a
> >> >>> text
> >> >>> file in the mobile documents folder that lists the current versions
> so
> >> >>> you
> >> >>> can easily compare that to the one on the server. After updating the
> >> >>> stacks, update the stored text file as well.
> >> >>>
> >> >>> If updates are mandatory, just skip the comparisons entirely and
> >> >>> force-download the updates. If only some of the stacks should be
> >> updated,
> >> >>> omit the ones that don't need to be updated from the server file.
> >> >>>
> >> >>> --
> >> >>> Jacqueline Landman Gay | jac...@hyperactivesw.com
> >> >>> HyperActive Software | http://www.hyperactivesw.com
> >> >>> On February 21, 2024 12:53:25 PM Mike Kerner via use-livecode
> >> >>>  wrote:
> >> >>>
> >> >>> > right - no updating the engine + runtime in this scenario, just
> the
> >> >>> > stacks + scripts, and perhaps plugins.
> >> >>> > we are going to continue to only privately distribute to our
> >> corporate
> >> >>> > clients, so the app store won't be part of the equation. that does
> >> not
> >> >>> mean
> >> >>> > that apple won't object, though (but, i believe the rules for
> >> privately
> >> >>> > distributed apps are much more lenient than for app store apps -
> at
> >> >>> least,
> >> >>> > they have been for us, up until now)
> >> >>> >
> >> 

Re: sideloading updates to mobile

[J. Landman Gay via use-livecode]

You can't add or change anything inside the app bundle so downloaded files 
have to go in specialFolderPath("documents"). Copy the originals from the 
resources folder to the documents folder on first launch so you always have 
a known file path location. Any file in documents will be overwritten with 
the new download if the file name is the same.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 29, 2024 7:31:28 AM Mike Kerner via use-livecode 
 wrote:



i haven't tried deploying to a device, yet, so bear with me:
when you load the updated stack/behavior/etc., are you saving it into the
app bundle, or elsewhere? on locked/single-app devices, persistence is the
thing (but i would imagine that it works the same on single-app devices as
it does for normal ones).

On Wed, Feb 28, 2024 at 10:12 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:


"Revert this stack". That just means "reload from disk". Or you can
specify
a different stack.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 28, 2024 8:12:57 PM Mike Kerner via use-livecode
 wrote:

> so, how do we force LC to reload the stack?
> i can force the script to reload, and replace it, but if i want to reload
> the stack, do i have to close it, replace it, and then open it?
>
> On Wed, Feb 21, 2024 at 8:28 PM Mike Kerner 
> wrote:
>
>> thanks, jlg. that's kind-of what i was thinking.
>>
>>
>> On Wed, Feb 21, 2024 at 4:58 PM J. Landman Gay via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>
>>> I've done this for several mobile apps. As long as the updates only
>>> reside
>>> in the app's sandboxed container, even the App Store doesn't care.
>>>
>>> Basically, I put a short text file on the server listing the update
>>> version(s) of the file(s), one per line if they are all different.
Every
>>> stack in the app suite has a custom property named cVersion. If
necessary
>>> you can also add the download URL to the same line. On launch, the app
>>> downloads and parses the text to see if the server version is different
>>> from the installed one. If so, it uses "put URL  into URL
>>> >> path>" to download and save the the updates to the mobile documents
>>> folder,
>>> overwriting the old ones.
>>>
>>> It's pretty simple, if I understand what you need correctly. I also
store
>>> other info in the the text file occasionally, such as a text string
>>> describing the updates so I can show an answer dialog if I want the
user
>>> to
>>> agree or decline the update (which will reappear on the next launch if
>>> they
>>> decline.)
>>>
>>> Sample text file is usually something like this:
>>>
>>>Stack 1  https://www.domain.com/updates/stack1.livecode
>>>Stack 2  https://www.domain.com/updates/stack2.livecode
>>>..
>>>This update provides new functionality and bug fixes.
>>>
>>> If you don't want to scan each stack for its cVersion, you can keep a
>>> text
>>> file in the mobile documents folder that lists the current versions so
>>> you
>>> can easily compare that to the one on the server. After updating the
>>> stacks, update the stored text file as well.
>>>
>>> If updates are mandatory, just skip the comparisons entirely and
>>> force-download the updates. If only some of the stacks should be
updated,
>>> omit the ones that don't need to be updated from the server file.
>>>
>>> --
>>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>>> HyperActive Software | http://www.hyperactivesw.com
>>> On February 21, 2024 12:53:25 PM Mike Kerner via use-livecode
>>>  wrote:
>>>
>>> > right - no updating the engine + runtime in this scenario, just the
>>> > stacks + scripts, and perhaps plugins.
>>> > we are going to continue to only privately distribute to our
corporate
>>> > clients, so the app store won't be part of the equation. that does
not
>>> mean
>>> > that apple won't object, though (but, i believe the rules for
privately
>>> > distributed apps are much more lenient than for app store apps - at
>>> least,
>>> > they have been for us, up until now)
>>> >
>>> > On Wed, Feb 21, 2024 at 12:53 PM Klaus major-k via use-livecode <
>>> > use-livecode@lists.runrev.com> wrote:
>>> >
>>> >> Hi Mike,
>>> >>
>>> >> > Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode <
>>> >> use-livecode@lists.runrev.com>:
>>> >> >
>>> >> > sorry that i was not clear. we've been using private deploys since
>>> around
>>> >> > 2010, using airlaunch to generate the bundle, and then uploading
to a
>>> >> > private url. that's not what i meant.
>>> >> > i'm talking about updating/patching an existing app, in place. the
>>> >> devices
>>> >> > are in single-app mode, so we would either have to pay for mdm and
>>> then
>>> >> use
>>> >> > that service to push app updates, OR, if we didn't use mdm, we
could
>>> have
>>> >> > the app pull the update and apply it.
>>> >> > i can kind-of guess how to make it

Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

i haven't tried deploying to a device, yet, so bear with me:
when you load the updated stack/behavior/etc., are you saving it into the
app bundle, or elsewhere? on locked/single-app devices, persistence is the
thing (but i would imagine that it works the same on single-app devices as
it does for normal ones).

On Wed, Feb 28, 2024 at 10:12 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> "Revert this stack". That just means "reload from disk". Or you can
> specify
> a different stack.
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On February 28, 2024 8:12:57 PM Mike Kerner via use-livecode
>  wrote:
>
> > so, how do we force LC to reload the stack?
> > i can force the script to reload, and replace it, but if i want to reload
> > the stack, do i have to close it, replace it, and then open it?
> >
> > On Wed, Feb 21, 2024 at 8:28 PM Mike Kerner 
> > wrote:
> >
> >> thanks, jlg. that's kind-of what i was thinking.
> >>
> >>
> >> On Wed, Feb 21, 2024 at 4:58 PM J. Landman Gay via use-livecode <
> >> use-livecode@lists.runrev.com> wrote:
> >>
> >>> I've done this for several mobile apps. As long as the updates only
> >>> reside
> >>> in the app's sandboxed container, even the App Store doesn't care.
> >>>
> >>> Basically, I put a short text file on the server listing the update
> >>> version(s) of the file(s), one per line if they are all different.
> Every
> >>> stack in the app suite has a custom property named cVersion. If
> necessary
> >>> you can also add the download URL to the same line. On launch, the app
> >>> downloads and parses the text to see if the server version is different
> >>> from the installed one. If so, it uses "put URL  into URL
> >>>  >>> path>" to download and save the the updates to the mobile documents
> >>> folder,
> >>> overwriting the old ones.
> >>>
> >>> It's pretty simple, if I understand what you need correctly. I also
> store
> >>> other info in the the text file occasionally, such as a text string
> >>> describing the updates so I can show an answer dialog if I want the
> user
> >>> to
> >>> agree or decline the update (which will reappear on the next launch if
> >>> they
> >>> decline.)
> >>>
> >>> Sample text file is usually something like this:
> >>>
> >>>Stack 1  https://www.domain.com/updates/stack1.livecode
> >>>Stack 2  https://www.domain.com/updates/stack2.livecode
> >>>..
> >>>This update provides new functionality and bug fixes.
> >>>
> >>> If you don't want to scan each stack for its cVersion, you can keep a
> >>> text
> >>> file in the mobile documents folder that lists the current versions so
> >>> you
> >>> can easily compare that to the one on the server. After updating the
> >>> stacks, update the stored text file as well.
> >>>
> >>> If updates are mandatory, just skip the comparisons entirely and
> >>> force-download the updates. If only some of the stacks should be
> updated,
> >>> omit the ones that don't need to be updated from the server file.
> >>>
> >>> --
> >>> Jacqueline Landman Gay | jac...@hyperactivesw.com
> >>> HyperActive Software | http://www.hyperactivesw.com
> >>> On February 21, 2024 12:53:25 PM Mike Kerner via use-livecode
> >>>  wrote:
> >>>
> >>> > right - no updating the engine + runtime in this scenario, just the
> >>> > stacks + scripts, and perhaps plugins.
> >>> > we are going to continue to only privately distribute to our
> corporate
> >>> > clients, so the app store won't be part of the equation. that does
> not
> >>> mean
> >>> > that apple won't object, though (but, i believe the rules for
> privately
> >>> > distributed apps are much more lenient than for app store apps - at
> >>> least,
> >>> > they have been for us, up until now)
> >>> >
> >>> > On Wed, Feb 21, 2024 at 12:53 PM Klaus major-k via use-livecode <
> >>> > use-livecode@lists.runrev.com> wrote:
> >>> >
> >>> >> Hi Mike,
> >>> >>
> >>> >> > Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode <
> >>> >> use-livecode@lists.runrev.com>:
> >>> >> >
> >>> >> > sorry that i was not clear. we've been using private deploys since
> >>> around
> >>> >> > 2010, using airlaunch to generate the bundle, and then uploading
> to a
> >>> >> > private url. that's not what i meant.
> >>> >> > i'm talking about updating/patching an existing app, in place. the
> >>> >> devices
> >>> >> > are in single-app mode, so we would either have to pay for mdm and
> >>> then
> >>> >> use
> >>> >> > that service to push app updates, OR, if we didn't use mdm, we
> could
> >>> have
> >>> >> > the app pull the update and apply it.
> >>> >> > i can kind-of guess how to make it work, but i'm sure there are a
> >>> couple
> >>> >> of
> >>> >> > tricks that i don't want to have to figure out, if someone else
> has
> >>> >> already
> >>> >> > figured it out.
> >>> >>
> >>> >> you could use the "splashscreen" approach to update one or more
> stacks,
> >>> >> but that will
> >>> >> of cour

Re: sideloading updates to mobile

[J. Landman Gay via use-livecode]

"Revert this stack". That just means "reload from disk". Or you can specify 
a different stack.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 28, 2024 8:12:57 PM Mike Kerner via use-livecode 
 wrote:



so, how do we force LC to reload the stack?
i can force the script to reload, and replace it, but if i want to reload
the stack, do i have to close it, replace it, and then open it?

On Wed, Feb 21, 2024 at 8:28 PM Mike Kerner 
wrote:


thanks, jlg. that's kind-of what i was thinking.


On Wed, Feb 21, 2024 at 4:58 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:


I've done this for several mobile apps. As long as the updates only
reside
in the app's sandboxed container, even the App Store doesn't care.

Basically, I put a short text file on the server listing the update
version(s) of the file(s), one per line if they are all different.  Every
stack in the app suite has a custom property named cVersion. If necessary
you can also add the download URL to the same line. On launch, the app
downloads and parses the text to see if the server version is different
from the installed one. If so, it uses "put URL  into URL
" to download and save the the updates to the mobile documents
folder,
overwriting the old ones.

It's pretty simple, if I understand what you need correctly. I also store
other info in the the text file occasionally, such as a text string
describing the updates so I can show an answer dialog if I want the user
to
agree or decline the update (which will reappear on the next launch if
they
decline.)

Sample text file is usually something like this:

   Stack 1  https://www.domain.com/updates/stack1.livecode
   Stack 2  https://www.domain.com/updates/stack2.livecode
   ..
   This update provides new functionality and bug fixes.

If you don't want to scan each stack for its cVersion, you can keep a
text
file in the mobile documents folder that lists the current versions so
you
can easily compare that to the one on the server. After updating the
stacks, update the stored text file as well.

If updates are mandatory, just skip the comparisons entirely and
force-download the updates. If only some of the stacks should be updated,
omit the ones that don't need to be updated from the server file.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 21, 2024 12:53:25 PM Mike Kerner via use-livecode
 wrote:

> right - no updating the engine + runtime in this scenario, just the
> stacks + scripts, and perhaps plugins.
> we are going to continue to only privately distribute to our corporate
> clients, so the app store won't be part of the equation. that does not
mean
> that apple won't object, though (but, i believe the rules for privately
> distributed apps are much more lenient than for app store apps - at
least,
> they have been for us, up until now)
>
> On Wed, Feb 21, 2024 at 12:53 PM Klaus major-k via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> Hi Mike,
>>
>> > Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode <
>> use-livecode@lists.runrev.com>:
>> >
>> > sorry that i was not clear. we've been using private deploys since
around
>> > 2010, using airlaunch to generate the bundle, and then uploading to a
>> > private url. that's not what i meant.
>> > i'm talking about updating/patching an existing app, in place. the
>> devices
>> > are in single-app mode, so we would either have to pay for mdm and
then
>> use
>> > that service to push app updates, OR, if we didn't use mdm, we could
have
>> > the app pull the update and apply it.
>> > i can kind-of guess how to make it work, but i'm sure there are a
couple
>> of
>> > tricks that i don't want to have to figure out, if someone else has
>> already
>> > figured it out.
>>
>> you could use the "splashscreen" approach to update one or more stacks,
>> but that will
>> of course only work if you do not want to update the actual
engine/runtime.
>>
>> However I'm not sure if Apple will allow this, no problem on Android
>> however.
>>
>>
>> Best
>>
>> Klaus
>>
>> --
>> Klaus Major
>> https://www.major-k.de
>> https://www.major-k.de/bass
>> kl...@major-k.de
>>
>>
>> ___
>> 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
>>
>
>
> --
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
>   and did a little diving.
> And God said, "This is good."
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.

Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

so, how do we force LC to reload the stack?
i can force the script to reload, and replace it, but if i want to reload
the stack, do i have to close it, replace it, and then open it?

On Wed, Feb 21, 2024 at 8:28 PM Mike Kerner 
wrote:

> thanks, jlg. that's kind-of what i was thinking.
>
>
> On Wed, Feb 21, 2024 at 4:58 PM J. Landman Gay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> I've done this for several mobile apps. As long as the updates only
>> reside
>> in the app's sandboxed container, even the App Store doesn't care.
>>
>> Basically, I put a short text file on the server listing the update
>> version(s) of the file(s), one per line if they are all different.  Every
>> stack in the app suite has a custom property named cVersion. If necessary
>> you can also add the download URL to the same line. On launch, the app
>> downloads and parses the text to see if the server version is different
>> from the installed one. If so, it uses "put URL  into URL
>> > path>" to download and save the the updates to the mobile documents
>> folder,
>> overwriting the old ones.
>>
>> It's pretty simple, if I understand what you need correctly. I also store
>> other info in the the text file occasionally, such as a text string
>> describing the updates so I can show an answer dialog if I want the user
>> to
>> agree or decline the update (which will reappear on the next launch if
>> they
>> decline.)
>>
>> Sample text file is usually something like this:
>>
>>Stack 1  https://www.domain.com/updates/stack1.livecode
>>Stack 2  https://www.domain.com/updates/stack2.livecode
>>..
>>This update provides new functionality and bug fixes.
>>
>> If you don't want to scan each stack for its cVersion, you can keep a
>> text
>> file in the mobile documents folder that lists the current versions so
>> you
>> can easily compare that to the one on the server. After updating the
>> stacks, update the stored text file as well.
>>
>> If updates are mandatory, just skip the comparisons entirely and
>> force-download the updates. If only some of the stacks should be updated,
>> omit the ones that don't need to be updated from the server file.
>>
>> --
>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
>> On February 21, 2024 12:53:25 PM Mike Kerner via use-livecode
>>  wrote:
>>
>> > right - no updating the engine + runtime in this scenario, just the
>> > stacks + scripts, and perhaps plugins.
>> > we are going to continue to only privately distribute to our corporate
>> > clients, so the app store won't be part of the equation. that does not
>> mean
>> > that apple won't object, though (but, i believe the rules for privately
>> > distributed apps are much more lenient than for app store apps - at
>> least,
>> > they have been for us, up until now)
>> >
>> > On Wed, Feb 21, 2024 at 12:53 PM Klaus major-k via use-livecode <
>> > use-livecode@lists.runrev.com> wrote:
>> >
>> >> Hi Mike,
>> >>
>> >> > Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode <
>> >> use-livecode@lists.runrev.com>:
>> >> >
>> >> > sorry that i was not clear. we've been using private deploys since
>> around
>> >> > 2010, using airlaunch to generate the bundle, and then uploading to a
>> >> > private url. that's not what i meant.
>> >> > i'm talking about updating/patching an existing app, in place. the
>> >> devices
>> >> > are in single-app mode, so we would either have to pay for mdm and
>> then
>> >> use
>> >> > that service to push app updates, OR, if we didn't use mdm, we could
>> have
>> >> > the app pull the update and apply it.
>> >> > i can kind-of guess how to make it work, but i'm sure there are a
>> couple
>> >> of
>> >> > tricks that i don't want to have to figure out, if someone else has
>> >> already
>> >> > figured it out.
>> >>
>> >> you could use the "splashscreen" approach to update one or more stacks,
>> >> but that will
>> >> of course only work if you do not want to update the actual
>> engine/runtime.
>> >>
>> >> However I'm not sure if Apple will allow this, no problem on Android
>> >> however.
>> >>
>> >>
>> >> Best
>> >>
>> >> Klaus
>> >>
>> >> --
>> >> Klaus Major
>> >> https://www.major-k.de
>> >> https://www.major-k.de/bass
>> >> kl...@major-k.de
>> >>
>> >>
>> >> ___
>> >> 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
>> >>
>> >
>> >
>> > --
>> > On the first day, God created the heavens and the Earth
>> > On the second day, God created the oceans.
>> > On the third day, God put the animals on hold for a few hours,
>> >   and did a little diving.
>> > And God said, "This is good."
>> > ___
>> > use-livecode mailing list
>> > use-livecode@lists.runrev.com
>> > Please visit this

Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

thanks, jlg. that's kind-of what i was thinking.


On Wed, Feb 21, 2024 at 4:58 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I've done this for several mobile apps. As long as the updates only reside
> in the app's sandboxed container, even the App Store doesn't care.
>
> Basically, I put a short text file on the server listing the update
> version(s) of the file(s), one per line if they are all different.  Every
> stack in the app suite has a custom property named cVersion. If necessary
> you can also add the download URL to the same line. On launch, the app
> downloads and parses the text to see if the server version is different
> from the installed one. If so, it uses "put URL  into URL
>  path>" to download and save the the updates to the mobile documents
> folder,
> overwriting the old ones.
>
> It's pretty simple, if I understand what you need correctly. I also store
> other info in the the text file occasionally, such as a text string
> describing the updates so I can show an answer dialog if I want the user
> to
> agree or decline the update (which will reappear on the next launch if
> they
> decline.)
>
> Sample text file is usually something like this:
>
>Stack 1  https://www.domain.com/updates/stack1.livecode
>Stack 2  https://www.domain.com/updates/stack2.livecode
>..
>This update provides new functionality and bug fixes.
>
> If you don't want to scan each stack for its cVersion, you can keep a text
> file in the mobile documents folder that lists the current versions so you
> can easily compare that to the one on the server. After updating the
> stacks, update the stored text file as well.
>
> If updates are mandatory, just skip the comparisons entirely and
> force-download the updates. If only some of the stacks should be updated,
> omit the ones that don't need to be updated from the server file.
>
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> On February 21, 2024 12:53:25 PM Mike Kerner via use-livecode
>  wrote:
>
> > right - no updating the engine + runtime in this scenario, just the
> > stacks + scripts, and perhaps plugins.
> > we are going to continue to only privately distribute to our corporate
> > clients, so the app store won't be part of the equation. that does not
> mean
> > that apple won't object, though (but, i believe the rules for privately
> > distributed apps are much more lenient than for app store apps - at
> least,
> > they have been for us, up until now)
> >
> > On Wed, Feb 21, 2024 at 12:53 PM Klaus major-k via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> >> Hi Mike,
> >>
> >> > Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode <
> >> use-livecode@lists.runrev.com>:
> >> >
> >> > sorry that i was not clear. we've been using private deploys since
> around
> >> > 2010, using airlaunch to generate the bundle, and then uploading to a
> >> > private url. that's not what i meant.
> >> > i'm talking about updating/patching an existing app, in place. the
> >> devices
> >> > are in single-app mode, so we would either have to pay for mdm and
> then
> >> use
> >> > that service to push app updates, OR, if we didn't use mdm, we could
> have
> >> > the app pull the update and apply it.
> >> > i can kind-of guess how to make it work, but i'm sure there are a
> couple
> >> of
> >> > tricks that i don't want to have to figure out, if someone else has
> >> already
> >> > figured it out.
> >>
> >> you could use the "splashscreen" approach to update one or more stacks,
> >> but that will
> >> of course only work if you do not want to update the actual
> engine/runtime.
> >>
> >> However I'm not sure if Apple will allow this, no problem on Android
> >> however.
> >>
> >>
> >> Best
> >>
> >> Klaus
> >>
> >> --
> >> Klaus Major
> >> https://www.major-k.de
> >> https://www.major-k.de/bass
> >> kl...@major-k.de
> >>
> >>
> >> ___
> >> 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
> >>
> >
> >
> > --
> > On the first day, God created the heavens and the Earth
> > On the second day, God created the oceans.
> > On the third day, God put the animals on hold for a few hours,
> >   and did a little diving.
> > And God said, "This is good."
> > ___
> > 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/m

Re: sideloading updates to mobile

[J. Landman Gay via use-livecode]

I've done this for several mobile apps. As long as the updates only reside 
in the app's sandboxed container, even the App Store doesn't care.


Basically, I put a short text file on the server listing the update 
version(s) of the file(s), one per line if they are all different.  Every 
stack in the app suite has a custom property named cVersion. If necessary 
you can also add the download URL to the same line. On launch, the app 
downloads and parses the text to see if the server version is different 
from the installed one. If so, it uses "put URL  into URL path>" to download and save the the updates to the mobile documents folder, 
overwriting the old ones.


It's pretty simple, if I understand what you need correctly. I also store 
other info in the the text file occasionally, such as a text string 
describing the updates so I can show an answer dialog if I want the user to 
agree or decline the update (which will reappear on the next launch if they 
decline.)


Sample text file is usually something like this:

  Stack 1  https://www.domain.com/updates/stack1.livecode
  Stack 2  https://www.domain.com/updates/stack2.livecode
  ..
  This update provides new functionality and bug fixes.

If you don't want to scan each stack for its cVersion, you can keep a text 
file in the mobile documents folder that lists the current versions so you 
can easily compare that to the one on the server. After updating the 
stacks, update the stored text file as well.


If updates are mandatory, just skip the comparisons entirely and 
force-download the updates. If only some of the stacks should be updated, 
omit the ones that don't need to be updated from the server file.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 21, 2024 12:53:25 PM Mike Kerner via use-livecode 
 wrote:



right - no updating the engine + runtime in this scenario, just the
stacks + scripts, and perhaps plugins.
we are going to continue to only privately distribute to our corporate
clients, so the app store won't be part of the equation. that does not mean
that apple won't object, though (but, i believe the rules for privately
distributed apps are much more lenient than for app store apps - at least,
they have been for us, up until now)

On Wed, Feb 21, 2024 at 12:53 PM Klaus major-k via use-livecode <
use-livecode@lists.runrev.com> wrote:


Hi Mike,

> Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode <
use-livecode@lists.runrev.com>:
>
> sorry that i was not clear. we've been using private deploys since around
> 2010, using airlaunch to generate the bundle, and then uploading to a
> private url. that's not what i meant.
> i'm talking about updating/patching an existing app, in place. the
devices
> are in single-app mode, so we would either have to pay for mdm and then
use
> that service to push app updates, OR, if we didn't use mdm, we could have
> the app pull the update and apply it.
> i can kind-of guess how to make it work, but i'm sure there are a couple
of
> tricks that i don't want to have to figure out, if someone else has
already
> figured it out.

you could use the "splashscreen" approach to update one or more stacks,
but that will
of course only work if you do not want to update the actual engine/runtime.

However I'm not sure if Apple will allow this, no problem on Android
however.


Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
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




--
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
  and did a little diving.
And God said, "This is good."
___
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

Re: sideloading updates to mobile

[Klaus major-k via use-livecode]

Hi Mike,

> Am 21.02.2024 um 20:17 schrieb Mike Kerner via use-livecode 
> :
> 
> mobile device management:
> https://en.wikipedia.org/wiki/Mobile_device_management
> it's like testflight on steroids. in our case, it would enable us to force
> app (and even os) updates on devices that are locked into single-app mode
> 
>>> i guess the other option would be to roll an mdm server 
>> sorry, but what does "mdm" mean?

thank you!


Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
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

Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

mobile device management:
https://en.wikipedia.org/wiki/Mobile_device_management
it's like testflight on steroids. in our case, it would enable us to force
app (and even os) updates on devices that are locked into single-app mode

On Wed, Feb 21, 2024 at 1:57 PM Klaus major-k via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Am 21.02.2024 um 19:51 schrieb Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com>:
> >
> > i guess the other option would be to roll an mdm server 
>
> sorry, but what does "mdm" mean?
>
> --
> Klaus Major
> https://www.major-k.de
> https://www.major-k.de/bass
> kl...@major-k.de
>
>
> ___
> 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
>


-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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

Re: sideloading updates to mobile

[Klaus major-k via use-livecode]

Am 21.02.2024 um 19:51 schrieb Mike Kerner via use-livecode 
:
> 
> i guess the other option would be to roll an mdm server 

sorry, but what does "mdm" mean?

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
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

Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

i guess the other option would be to roll an mdm server 

On Wed, Feb 21, 2024 at 1:50 PM Mike Kerner 
wrote:

> right - no updating the engine + runtime in this scenario, just the
> stacks + scripts, and perhaps plugins.
> we are going to continue to only privately distribute to our corporate
> clients, so the app store won't be part of the equation. that does not mean
> that apple won't object, though (but, i believe the rules for privately
> distributed apps are much more lenient than for app store apps - at least,
> they have been for us, up until now)
>
> On Wed, Feb 21, 2024 at 12:53 PM Klaus major-k via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> Hi Mike,
>>
>> > Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode <
>> use-livecode@lists.runrev.com>:
>> >
>> > sorry that i was not clear. we've been using private deploys since
>> around
>> > 2010, using airlaunch to generate the bundle, and then uploading to a
>> > private url. that's not what i meant.
>> > i'm talking about updating/patching an existing app, in place. the
>> devices
>> > are in single-app mode, so we would either have to pay for mdm and then
>> use
>> > that service to push app updates, OR, if we didn't use mdm, we could
>> have
>> > the app pull the update and apply it.
>> > i can kind-of guess how to make it work, but i'm sure there are a
>> couple of
>> > tricks that i don't want to have to figure out, if someone else has
>> already
>> > figured it out.
>>
>> you could use the "splashscreen" approach to update one or more stacks,
>> but that will
>> of course only work if you do not want to update the actual
>> engine/runtime.
>>
>> However I'm not sure if Apple will allow this, no problem on Android
>> however.
>>
>>
>> Best
>>
>> Klaus
>>
>> --
>> Klaus Major
>> https://www.major-k.de
>> https://www.major-k.de/bass
>> kl...@major-k.de
>>
>>
>> ___
>> 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
>>
>
>
> --
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
>and did a little diving.
> And God said, "This is good."
>


-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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

Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

right - no updating the engine + runtime in this scenario, just the
stacks + scripts, and perhaps plugins.
we are going to continue to only privately distribute to our corporate
clients, so the app store won't be part of the equation. that does not mean
that apple won't object, though (but, i believe the rules for privately
distributed apps are much more lenient than for app store apps - at least,
they have been for us, up until now)

On Wed, Feb 21, 2024 at 12:53 PM Klaus major-k via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hi Mike,
>
> > Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com>:
> >
> > sorry that i was not clear. we've been using private deploys since around
> > 2010, using airlaunch to generate the bundle, and then uploading to a
> > private url. that's not what i meant.
> > i'm talking about updating/patching an existing app, in place. the
> devices
> > are in single-app mode, so we would either have to pay for mdm and then
> use
> > that service to push app updates, OR, if we didn't use mdm, we could have
> > the app pull the update and apply it.
> > i can kind-of guess how to make it work, but i'm sure there are a couple
> of
> > tricks that i don't want to have to figure out, if someone else has
> already
> > figured it out.
>
> you could use the "splashscreen" approach to update one or more stacks,
> but that will
> of course only work if you do not want to update the actual engine/runtime.
>
> However I'm not sure if Apple will allow this, no problem on Android
> however.
>
>
> Best
>
> Klaus
>
> --
> Klaus Major
> https://www.major-k.de
> https://www.major-k.de/bass
> kl...@major-k.de
>
>
> ___
> 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
>


-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
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

Re: sideloading updates to mobile

[Klaus major-k via use-livecode]

Hi Mike,

> Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode 
> :
> 
> sorry that i was not clear. we've been using private deploys since around
> 2010, using airlaunch to generate the bundle, and then uploading to a
> private url. that's not what i meant.
> i'm talking about updating/patching an existing app, in place. the devices
> are in single-app mode, so we would either have to pay for mdm and then use
> that service to push app updates, OR, if we didn't use mdm, we could have
> the app pull the update and apply it.
> i can kind-of guess how to make it work, but i'm sure there are a couple of
> tricks that i don't want to have to figure out, if someone else has already
> figured it out.

you could use the "splashscreen" approach to update one or more stacks, but 
that will 
of course only work if you do not want to update the actual engine/runtime.

However I'm not sure if Apple will allow this, no problem on Android however.


Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de


___
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

Re: sideloading updates to mobile

[Mike Kerner via use-livecode]

sorry that i was not clear. we've been using private deploys since around
2010, using airlaunch to generate the bundle, and then uploading to a
private url. that's not what i meant.
i'm talking about updating/patching an existing app, in place. the devices
are in single-app mode, so we would either have to pay for mdm and then use
that service to push app updates, OR, if we didn't use mdm, we could have
the app pull the update and apply it.
i can kind-of guess how to make it work, but i'm sure there are a couple of
tricks that i don't want to have to figure out, if someone else has already
figured it out.
___
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

Re: sideloading updates to mobile

[Andrew at MWCM via use-livecode]

Sideloading to iOS itself is fairly easy, even easier with Jacque’s wonderful 
tool AirLaunch (which allows you to post a link online for the end-user to 
visit and install from w/o being on-site). The biggest hurdle I have found is 
that you must first obtain the UDID of the specific device you want to side 
load to AND THEN create a new Provisioning Profile in the Apple Developer 
portal which includes that test device before you build. 

Without going through that process first you can build and submit to Apple 
using TestFlight which makes the update available to non-UDID obtained devices 
but is subject to the standard Apple approval process (which has taken between 
4 hours and 2 weeks for me to pass over the years).

- Andrew Bell

> anyone screw around with sideloading updates to mobile?
> it should be pretty straightforward, but i haven't messed with it, yet.
> one of our apps runs on single-app-mode ios devices. so, we could pay for
> mdm to update it, or we could sideload the updates.


___
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

sideloading updates to mobile

[Mike Kerner via use-livecode]

anyone screw around with sideloading updates to mobile?
it should be pretty straightforward, but i haven't messed with it, yet.
one of our apps runs on single-app-mode ios devices. so, we could pay for
mdm to update it, or we could sideload the updates.
___
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