MackeyK24 Posted March 14, 2018 Share Posted March 14, 2018 Yo @Deltakosh I see your samples now using this new BABYLON.GUI stuff. What is the main reasons for using this babylon gui vs using regular html markup for NON-3D guis, like huds etc. I can see when you need to attach some 2D gui to a 3D Object in the scene. But if is just SCREEN OVERLAY stuff like sliders and buttons and text... What advantage does BABYLON.Gui have over regular HTML markup ??? JackFalcon 1 Quote Link to comment Share on other sites More sharing options...
RaananW Posted March 14, 2018 Share Posted March 14, 2018 simply put - some devices only support a single canvas and no html elements. the best example is VR, where you can project the canvas to the headset, but not anything else. same goes to mobile experiences. Besides, with HTML you need to take care of scaling the objects and responsibility (and use CSS! Yuck....). JackFalcon 1 Quote Link to comment Share on other sites More sharing options...
MackeyK24 Posted March 22, 2018 Author Share Posted March 22, 2018 On 3/13/2018 at 10:18 PM, RaananW said: simply put - some devices only support a single canvas and no html elements. the best example is VR, where you can project the canvas to the headset, but not anything else. same goes to mobile experiences. Besides, with HTML you need to take care of scaling the objects and responsibility (and use CSS! Yuck....). Im luvin the new Babylon GUI JackFalcon 1 Quote Link to comment Share on other sites More sharing options...
Guest Posted March 23, 2018 Share Posted March 23, 2018 Me too Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.