4 ms·
That's exactly what we encourage :) composition of higher level components that render down to other high level components that eventually render to (virtual) D
by peterhunt 13y ago
That's exactly what we encourage :) composition of higher level components that render down to other high level components that eventually render to (virtual) DOM.
- jarpineh 13y agoI wonder if this approach would work with visual XML (Docbook) and HTML editing, where resulting DOM can be complex and large. Competent writer might generate loads of input (writing 100 letters per minute, copy-paste). If my writing tool has latencies, that annoys me far more than game latency. Other approach I have been testing is contenteditable, but this won't work with virtual DOM at all. Though how you parse an existing XML document to React's virtual DOM is beyond me. Perhaps you have to generate function calls SAX style.
- peterhunt 13y agoWe could do that probably. Would need your own parser With content editable we can just parse he html. We have an example in the repo.
- jarpineh 13y ago> We could do that probably. Would need your own parser Parser for HTML and XML to generate React components and generate virtual DOM from that? This got me thinking. > With content editable we can just parse he html. We have an example in the repo. It must be the weekend denseness setting in... I grepped through React repo, but I just found bits in the core that had something to do with content editable. Could you perhaps point me to right direction? If I understand this correctly, I could parse the entered HTML to virtual DOM.