Forums

Looking at the source for Y.View

in the initializer there is the following comment:

// When the container node changes (or when it's set for the first
// time), we'll attach events to it, but not until then. This allows the
// container to be created lazily the first time it's accessed rather
// than always on init.
this.after('containerChange', this._afterContainerChange);

The wording 'changes' is what I am getting at.

However the ATTRS for container are:

container: {
getter : '_getContainer',
setter : Y.one,
writeOnce: true
}

Why is the container a writeOnce attribute? In my application I want to use a nested (subview). when the parent view changes, I want to update the container for the subview so I dont have to keep creating a new subview. But I cant! I guess there is some rational behind this which I would be interested in finding out, otherwise lets remove the writeOnce!

Thanks,

Richard.

Well I had filed a Bug with the same thing and after some discussion it go closed. As I worked more with Y.View I realized that having it writeOnce is actually a good strategy.

Even though you can not set the container after init, you can almost certainly do this.get('container').setHTML(Subview.render().get('container')) as many times as you want.