He's using the asset pipeline instead of including javascript, so changing the javascript includes on a page-by-page basis isn't as easy as it is without the asset-pipeline.
It's not clear that you'd want to, either. In production mode, all the js gets concatenated and minified by the asset pipeline into one big blob that is presumably cached by the browser. If two pages have different javascripts, that means there's two big blobs that have to be transferred and cached, even if one blob is smaller than the other. Different javascript per page also breaks the new push-state option in Hobo 2.0, as well as the pjax plugin. Speaking of pjax, has anybody tried it with Hobo yet? It or one of its alternatives is one of those things that I'd like to try out, but haven't got around to yet. Bryan -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
