Jump to content

BABYLON GUI vs HTML MARKUP


MackeyK24
 Share

Recommended Posts

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 ???

Link to comment
Share on other sites

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....).

Link to comment
Share on other sites

  • 2 weeks later...
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 :)

 

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...