Streamed HTML as discussed here: The weirdly obscure art of Streamed HTML looks nice for performance enhancement.
I got an idea to have something similar in enaml-web but don't know if realistic:
I think we can add a "compute_order"property to Tag (default to 1). At the first pass for render, the engine will only compute Nodes (Tags) with compute_order=1 and send result to the browser. A second pass is done for rendering nodes with "compute_order=2". New nodes and updates are send to the client with websocket.
Do you thing it can be a good approach ?
Do you think it can be achieved without rewriting all enaml ?
Streamed HTML as discussed here: The weirdly obscure art of Streamed HTML looks nice for performance enhancement.
I got an idea to have something similar in enaml-web but don't know if realistic:
I think we can add a "compute_order"property to Tag (default to 1). At the first pass for render, the engine will only compute Nodes (Tags) with compute_order=1 and send result to the browser. A second pass is done for rendering nodes with "compute_order=2". New nodes and updates are send to the client with websocket.
Do you thing it can be a good approach ?
Do you think it can be achieved without rewriting all enaml ?