This all brings up another problem I've run into. I was thinking of creating a rich_type for the kendo editor based off of the html type. The only purpose would be to create a custom input that adds the kendo javascript to turn the text area into the editor. However this would put javascript in the middle of the page and wont work with bottom loading of javascript since the inline code will get hit before jquery is loaded and bomb. Given what you have said perhaps it is better off if I just add the javascript to the page and not worry about it. After all in the grand scheme of things its really not a lot of code. The real bulk of the code, the kendo ui stuff, is being added to every page anyway.
Bob On Tuesday, October 9, 2012 8:45:32 AM UTC-4, Bryan Larsen wrote: > > 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 view this discussion on the web visit https://groups.google.com/d/msg/hobousers/-/gKeb_6mUvV0J. 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.
