You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 23, 2019. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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.
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 currenttext-editor*.js
implementation to create a fallbackDOMRenderer
class forTextPlane
?The text was updated successfully, but these errors were encountered: