7 ms·
I am curious if you liked it or moved to another tool. edit: I know it's still early, but I'm trying to introduce something new beyond `pointer-events` and mor
by jimmy2020 6y ago
I am curious if you liked it or moved to another tool.
edit: I know it's still early, but I'm trying to introduce something new beyond `pointer-events` and more into studying each node and its effect on the entire dom tree.
- verdverm 6y agoMoved on, GPL-3 is a non-starter. Working on something with GrapesJS. Are you saying something like "notify" rather than "check for changes" with shadow dom? What is studying -> effect? (in more detail)
- jimmy2020 6y agoWell yes. Thanks. It's exactly "notify" -> click on the node -> node is now ready to move -> function executes desirable effects to all DOM tree based on the movement - It's not framework. You can implement this solution regardless of what you are using. Even async rendering. It doesn't matter how you start rendering. From above to root or otherwise. - This is the only solution, taking into consideration the above pontins, that executes "stream of write requests" to the browser. It doesn't write/read then do it again. No lagging. All manipulation runs smoothly 60fps. - Every change in DOM is registered and updated in the DOM store and exposed. So you can implement (any DOM manipulation) whenever you need in your app.