> It only helps some games. Most game development efforts will likely be > unaffected, since it's generally easiest to use an existing engine, > which will already have such things handled. > > Most games will either just use overlayed HTML, or have an in-engine > solution for UI. The desire to embed web elements in a scene itself is > relatively rare. (Certainly few existing games do this)
I think you're right about traditional games being built on top of portable middleware. However, at the last GDC, I did have a few devs specifically ask about doing this. They were using middleware, but building an interactive experience specifically for the web (iirc, in one case, the dev had built a little 3d coal mine in Unreal Editor to go along with a news article about a coal mine accident) and then it's totally natural to want to throw a <video> or tweet into the scene b/c hey, it's the web, they're used to doing stuff like that. FWIW, I was wondering if we could go a step further and allow (optional) user interaction with the rendered DOM elements. That way you could, say, select text on a 3d surface with a mouse or use an <input> tag. It seems like this would be possible if the vertex/pixel shaders were constrained to, say, affine transformations which starts to sound rather similar to the whitelisting approach mentioned elsewhere in this thread for mitigating timing attacks. _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
