configurable cache element

[turbolinks]

configurable cache element

[dhh]

Pjax is a good fit for when you don't want to use the full page. It doesn't fit into my vision of what turbolinks should be, though.

On Oct 2, 2012, at 10:07 PM, Richard Taylor wrote:

I've just hacked together a quick implementation of specifying a configurable cache element, so you can do something like this:

Turbolinks.setup({cache_id: 'main_container'});

For instances where you don't want to refresh the entire body. I have this requirement on two projects I'm working on so thought it might be a common case. Thoughts?

—
Reply to this email directly or view it on GitHub.

[dhh]

Although do share the specifics of your requirement. Curious to hear when full-page doesn't fit.

[moomerman]

Fair enough. The most recent case is a persistent visible audio player on the page with play progress indicator, I don't want that reloading on each page load.

[dhh]

Gotcha. Pjax is probably a better fit for that, then.

[pomartel]

@moomerman You could also try what I do with the Facebook SDK and keep your player alive by detaching that content from the DOM tree before fetching the new page. I'm not sure that would work with an audio player though. Some code here #62