Nice one! I'd also be interested in learning a technique to handle updates done offline. I e offline/online syncing.
Also, I was thinking about a way to force the manifest to reload. How about adding a field to the user model (assuming we're working on a multi user app) called manifest_version. Then for each create/update or destroy this version is increased. Further a new view is created that simply renders this version. The path to this view is then added to the application.manifest. Upon reloading the manifest the browser should then notice a change in the manifest and the new manifest would be loaded. Am I making any sense here? :)
I'm with @miguelsan and @Tilo. My spontaneous thought too was that this should be in Rails core.
To answer my (amnd @Gnagos') previous question: https://github.com/loopj/jquery-tokeninput/issues#issue/11
I'm also interested in knowing the answer to @Gnago's question. Anyone?
Nice one! I'd also be interested in learning a technique to handle updates done offline. I e offline/online syncing.
Also, I was thinking about a way to force the manifest to reload. How about adding a field to the user model (assuming we're working on a multi user app) called manifest_version. Then for each create/update or destroy this version is increased. Further a new view is created that simply renders this version. The path to this view is then added to the application.manifest. Upon reloading the manifest the browser should then notice a change in the manifest and the new manifest would be loaded. Am I making any sense here? :)