Sannyasin Brahmanathaswami wrote:
> 1) does it make sense to build this dynamically as needed from script
> using "create" and then you put this "create control" script into a
> library? It has the advantage of no binary object, so you can keep it
> in your text only "stacks" .livecodescript, but could be slow?
> 2) is it faster (on Android or iOS especially) to create it as a
> template group then use
> copy grp "info-display" of card 1 of stack "dialog-templates" to this
> What has your experience led you to choose as your best practice and
> why and how do you do it?
In general I try to "go to TOWN": Touch Only What's Needed.
If I don't need to create an object I probably won't, adjusting an
existing object instead. It only saves one step, but its a savings just
If you're committed to a script-only stack there's no decision to make:
every control must be instantiated dynamically, because a script-only
stack contains the stack script only, no objects.
Which reminds me: before I run off an spend an afternoon writing one,
has anyone here written a tool that reads a stack laid out with objects
and produces the script needed to recreate it from a script-only stack?
Seems tedious to write, but less tedious than writing instantiation code
for every property of every object of every card of every stack I might
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription