@mmckegg has an idea, instead of only listening to changes in the virtual dom data to trigger re-renders of the dom, what if we had two-way data binding between the dom and the virtual dom data: when the dom changes, we update the virtual dom data; when the virtual dom data changes, we update the dom (as we already do).
benefits:
editing your site becomes so easy, we all edit our sites through the chrome inspector anyways before then we have to code them. what if editing it through the inspector got saved, with support for time travel!
open questions:
what do we do about event listeners? (the javascript functions within our virtual dom data that don't get persisted to the dom inspector)
how do we edit the content data while editing our dom?
mmckegg
commented
9 years ago
@mmckegg has an idea, instead of only listening to changes in the virtual dom data to trigger re-renders of the dom, what if we had two-way data binding between the dom and the virtual dom data: when the dom changes, we update the virtual dom data; when the virtual dom data changes, we update the dom (as we already do).
benefits:
open questions: