On Monday, January 9, 2017 at 11:24:57 AM UTC, Rupert Smith wrote: > > Some or all of the page rendering is done server side, then whatever has > been rendered plus the application state is handed over to the client, and > the client displays it or completes or enhances the rendering. >
A wee problem with this. I don't see how a page can be partially rendered server side then passed to the client to complete, when using a virtual dom. Suppose for example that my pages are running with Main.fullscreen(), I can't just take the DOM that was rendered on the server, set it up as the virtual dom, and then have the client make changes to it as deltas to the DOM. I could just delete all of the server rendered DOM and replace it with the client rendered one through ELM, but you will see the screen blink as this happens. I guess therefore, that we are limited to all or nothing rendering on one side or the other, for any given DOM subtree? I can see how within a page their could be multiple Elm Html.programs attached to different sections of the page, and during the server rendering they might just act as placeholders for content that will only be rendered client side. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
