Musings on Architect, MVC, Nested Behaviors

Richard Gaskin ambassador at
Thu Dec 27 21:52:47 EST 2018

J. Landman Gay wrote:

 > On December 27, 2018 2:36:16 PM Richard Gaskin via use-livecode
 > <use-livecode at> wrote:
 >> Sounds like one more reason to allow stack properties as YAML
 >> frontmatter in the file.  Ever since I suggested that a couple
 >> years back, the range of valuable use-cases keeps growing.
 > I wouldn't mind if you poked them again about it.

At your prompting I started to open an enhancement request for this, but 
not long into it I hit on why they probably haven't done this yet:

By what means would be indicate which properties we want saved there and 
which ones we don't care about?

For example, we only care about the behavior property if it's non-empty.

Should that same rule apply to breakpoints?  Would there be cases where 
we wouldn't want them included?

We probably don't want the rect saved, but what if someone does?  How 
would they indicate to save the rect?

And so on for colors, and the rest.

I'm assuming customProps should always be there, yes?  Are there cases 
where they shouldn't?

Help answer these and I'll submit the request for their consideration.

  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  Ambassador at      

More information about the Use-livecode mailing list