I'd make it a script-only stack, and then
start using stack "..."
(probably in an openstack handler - but could be anywhere you like for
your own use).
By far the easiest to share (and for others to accept when shared).
Alex.
P.S. And, should this library be useful in LCServer context, it means
you can upload the stack to the server without getting annoying error
messages about mixed line endings which Coda-2 and some others give on
binary stacks).
On 29/12/2020 19:34, Ben Rubinstein via use-livecode wrote:
What is the best way to structure a library these days?
Currently I've got buttons with a script, and a 'mouseup' handler to
'insert the script of me into back' in my object library. But I don't
think that's very modern.
What's the right way to do it? Especially if I want to share it?
TIA,
Ben
_______________________________________________
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
