4 ms·
The author mentioned in the post that he didn't know anything about the dom at the time of writing it.
by leichtgewicht 12y ago
The author mentioned in the post that he didn't know anything about the dom at the time of writing it.
- je42 12y agointeresting decision: learning dom+css vs rewriting a complete UI layer in webgl.
- k__ 12y agolol, tells you much about the DOM and CSS, hu? ;)
- moron4hire 12y agoDOM isn't so much an issue, and actually makes a lot of sense when you think about the requirements it has to fulfill. It's just that no two browsers do it the same. I personally consider DOM and CSS as the least-evil-of-all-options for doing cross-platform UI. Not that a better solution couldn't be made, but all other current solutions for the type of software I want to make are worse than DOM in some way.
- k__ 12y agoSame here :)
- moron4hire 12y agoI don't know if this was at all on the author's mind, but by implementing the GUI in WebGL vs. DOM, they can now composite the GUI with the scene, rather than the GUI being strictly limited to the front of everything 3D. It's why I wrote Primrose[1], as source control editor that renders to Canvas instead of DOM. I intend to toss these things into 3D space. [1] shameless plug: http://capnmidnight.github.io/Primrose/ http://capnmidnight.github.io/Primrose/
- je42 12y agoIn your case it makes perfectly sense; except in the case of this topic the controls all seem to be overlays i.e. are never part of the scene.