Do script-only stacks support "chained" behaviors?

[Mike Kerner]

@Geoff, well, then my work here is done!
@Dr Hawk, do you mean in general?  That would require a change in LC, too,
and if we were going to do that, then I'd want it to be more LC-like,
perhaps with a handler.

On Mon, Jan 22, 2018 at 1:28 PM, Dr. Hawkins via use-livecode <
use-livecode at lists.runrev.com> wrote:

> On Mon, Jan 22, 2018 at 6:10 AM, Mike Kerner via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>
> >
> > The way he suggested structuring the projects was putting the ui elements
> > and their behaviors into /ui/stackName (and then the behaviors for that
> > stack into /ui/stackName/behaviors/).
>
>
> How about something similar to the unix convention of  indicating the shell
> to use in the first line of a text executable (e.g., #!/bin/tcsh ) as a
> comment?
>
> so the first line starting with, perhaps, "--#" would indicate that  what
> follows is an expression which evaluates to a button or other stack that is
> to be the behavior of the stack?
>
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> _______________________________________________
> 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
>



-- 
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."