Forums

I have a number of views in the app which may not actually render when the app changes the active view to them because their model data is not yet loaded. I was using the app to default a loading spinner on the navigate event, and then listening for a '*:rendered' event that would be bubbled from the views, to turn of the loading image.

unfortunately when I fire an event in my view's render method it does not bubble to the App, I am guessing because its not finished the render phase it's not yet a bubble target. what is the best way to approach this?

just to clarify the view's render method will do nothing if model data is not loaded and not fire the event, but the initializer sets up a call to render after the model data is loaded, on this occassion the render method will 'actually' render and fire the "rendered" event.

Thanks

Richard.

Hi Richard, your correct it isn't yet a bubble target.

If you want something to happen after the view is ready you can put it in the callback of showView() http://yuilibrary.com/yui/docs/api/clas ... d_showView

I made a module to help with firing a loading sequence with Y.App which you may find useful http://yuilibrary.com/gallery/show/app-loading Unfortunately I haven't put it on the CDN because I haven't had a chance to make any demo's, documentation or do proper testing on it but we are using it on 2 live apps without issue.

Jeff

I updated your fiddle to use the callback http://jsfiddle.net/bvxh6/2/ (open your console to see the logs)

actually, looking at this, the callback as the view instance, so I could set an attribute in the view to pass rendered state and introspect this in the callback. After that the app is a bubble target to any delayed rendering anyway so I can use on("*:rendered". So all in all I think this can be covered off now!?

Is there any logic/reason as to how and when the app establishes itself as a bubble target? This would be much neater if I could fire the rendered event from the render method.

Thanks for your help

Richard.

The timing of when the view's events will start bubbling to the app is something that I want to address. I've been hearing feedback like this that points me to the direction that the `view.addTarget(app)` call should happen sooner, and before the view's `render()` method is called.

There's one change going into 3.5.1 that allows you to affect whether a view will be rendered (or re-rendered in the case of a preserved view) or not: `app.showView('foo', null, {render: false})`. You can see more details about this change here:
https://github.com/yui/yui3/commit/3385 ... de6ff3b65a

There are some high level ideas of where I want to take Y.App's view management captured in TODOs:
https://github.com/yui/yui3/blob/master ... ase.js#L18

Those are all things I'm thinking about and plan to flush out for 3.6.0 to make the view management more robust and possibly reusable as a class extension for mixing into Y.View subclasses as well.