One issue that occurs to me is that in Hype, we get elements using HypeDocument.getElement . . . whereas a framework like view would need to get access the DOM directly. Would this be a problem?
I don’t have experience using this, but in regards to the
document.getElementById, the only difference is that the hypeDocument one is more resilient in the face of conflicts caused by multiple hype documents on a single .html page. Hype absolutely requires unique element IDs, so it may rename your requested ID in a case of collision. If there’s no collisions it is identical to
document.getElementById. Hype does do a lot of management of the DOM itself, so I’d think there are possibilities of Vue.js and Hype’s views of the world differing and causing issues, but who knows :).
Thanks @jonathan. There would definitely only be one Hype document per page, so that doesn’t seem like it would be a problem. That’s good to know. Also, I would only be operating on rects with inner html set dynamically - no video or other Hype Elements being used. Hype actually makes a good client for a web app.
If there’s any tips or tricks you come up with, please do share those!
this is an interesting topic. Putting VUE.js inside of Hype shouldn’t be a problem. At least when sticking it into a container. As for managing state across the whole document I do suspect that the virtual DOM and Hypes DOM management could/would collide (but I certainly would like to test it).
For a test I just used the MarkDown Editor Example from the VUE.js page and transferred it into Hype.
See this thread: