Forums

Marc,

This is a great question. I've been experimenting with some different approaches of solving this with the hope that we can provide a streamlined solution in YUI.

The basic idea behind the approaches I've been taking is to serialize the data the server is using to render the page (the models and model lists) to JSON, and dump that data into a <script> element within the HTML document the server is creating. If you're Gzipping the HTML pages (which you should) the amount of extra KB-weight will be minimal as gzipping is good at handling duplicate strings. Then the JavaScript running in the browser can revive that state and take over from there.

You can see this being done in Photos Near Me:

Server serializes the data it's using to render the HTML:
https://github.com/ericf/photosnear.me/ ... s#L130-147

Placeholders in the HTML for that data:
https://github.com/ericf/photosnear.me/ ... ars#L33-53

Client-side JavaScript reviving state and taking control:
https://github.com/ericf/photosnear.me/ ... rs#L55-102

I hope that helps guide you to something that will work for your app. Once this pattern becomes more fully baked and support widgets revivification through the same conduit, I hope to make it a feature of YUI.

Also it's really great to see you taking this approach of utilizing both the server and client to make your app awesome

I'm not sure I follow you, can you elaborate on what you mean and how you'd do it differently?



That's what this is doing, it's calling `showView()` and passing `render: false` as an option. Which tells the Y.App instance to not render the view (since it is already rendered by the server.)