What is your best practice for setting a script in a script?
craig at starfirelighting.com
Fri Jul 21 13:16:08 EDT 2023
I assume you have a blueprint of what will become a stack with at least one card? And that stack will possibly contain other cards, controls, scripts and behaviors?
But since all objects have properties, including scripts, and since LC has the “create” command, whatever you want to do seems straightforward, if not simple.
You must have the IDE open to even start, of course, so you are already “in” LC. Why not just do it the old fashioned way? The end result will be a stack, correct? What is the advantage of not starting with a stack?
> On Jul 21, 2023, at 12:10 PM, Paul Dupuis via use-livecode <use-livecode at lists.runrev.com> wrote:
> As some people on this list and the forums have explored in the past, I have a interest in creating a Livecode application (stack) entirely from a (text only) single script. So there are initially no Livecode objects to place a behavior script in. There are initially no buttons, fields, cards, stacks, or anything else.
> Yes, one of the values of Livecode is an interactive IDE for UI design (and refinement), but for this specific interest, it is all about creating the UI - in fact the whole app - from a single script.
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode