Skip to content
This repository has been archived by the owner on Jul 23, 2019. It is now read-only.

DOM Fallback Implementation. #99

Closed
ZehCnaS34 opened this issue May 30, 2018 · 1 comment
Closed

DOM Fallback Implementation. #99

ZehCnaS34 opened this issue May 30, 2018 · 1 comment

Comments

@ZehCnaS34
Copy link

Hi,

I’m using relatively old and obscure hardware (AMD A8-3850 APU), and have noticed that webgl2 is not available in electron/chrome. In the future, will Xray support some sort of DOM fallback for text_plane.js? If not, how difficult would it be to utilize Atom’s current text-editor*.js implementation to create a fallback DOMRenderer class for TextPlane?

@as-cii
Copy link
Contributor

as-cii commented May 31, 2018

Hello @ZehCnaS34, thanks for this question. Our current plan is to implement a WebGL1 fallback when WebGL2 isn't available. WebGL1 support seems to be pretty widespread and we should first consider that before investing time in a DOM implementation which, based on our experience on Atom, would be much slower.

According to https://caniuse.com/#feat=webgl, support for WebGL1 on desktop machines is almost 99% (WebGL2, by comparison, is supported only on ~75% of the tracked desktop machines), so I think it's very likely it would be supported on your machine as well.

@as-cii as-cii closed this as completed May 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants