Update strategy?

Graham Samuel livfoss at mac.com
Wed May 10 14:00:23 EDT 2017

Yes, but what if you want to update the launcher itself? Maybe I have made my ‘splash’ stack too rich in function, but I can easily see it needing revision. Because of this, I’m thinking of altering the structure of the app so that the update code is more or less all that is in the standalone recognised by the operating system, and all other stacks (including 90 percent of the original splash stack) are simply downloaded after the decision whether to update is made. Or is this stupid?

Thanks as ever for your reply.


> On 10 May 2017, at 19:08, J. Landman Gay via use-livecode <use-livecode at lists.runrev.com> wrote:
> On 5/10/17 8:10 AM, Graham Samuel via use-livecode wrote:
>> I have already got the idea of the text file and the test you
>> mention. I now have to experiment with the “open invisible” approach.
>> I have had so many problems with the IDE when trying to open two
>> stacks with the same name (it’s impossible AFAIKR - because LC
>> doesn’t have any hierarchical concept of stack names).
> I put the update code into the standalone launcher, and run it before it opens the data stack. That way you don't have two data stacks at the same time.
> -- 
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
> _______________________________________________
> 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