Here's a newbie question:
I thought I had understood that the .a.yaml file provides a highly abstract, clutter-free specification of the UI, while the .u.yaml (which, in its basic form, is "compiled" from the .a.yaml) can be augmented for low-level visual fine-tuning and/or more complex behaviour.
But then I would assume that the (optional) property persistentItems would belong into the .a.yaml, because it is neither complex nor a low-level detail of UI behaviour. However, it seems to be exclusive to the .u.yaml.
This is (at least for me) not just an academic question. As a newbie, I feel much more comfortable editing the .a.yaml than the .u.yaml, whose details I haven't really grasped.
So what is the rationale for having persistentItems exclusively in the .u.yaml?
But maybe I am still struggling with the concepts and have things messed up in my brain. Any enlightenment is welcome!
\Gisbert
Why persistentItems in .u.yaml rather than in .a.yaml?
Re: Why persistentItems in .u.yaml rather than in .a.yaml?
hey,
i'd have to think about it, hey. we did write a lot of this stuff quite a while ago!
jonathon
i'd have to think about it, hey. we did write a lot of this stuff quite a while ago!
jonathon