8000 getBoxQuads Polyfill · Issue #309 · lume/lume · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

getBoxQuads Polyfill #309

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jogibear9988 opened this issue Aug 19, 2024 · 1 comment
Open

getBoxQuads Polyfill #309

jogibear9988 opened this issue Aug 19, 2024 · 1 comment

Comments

@jogibear9988
Copy link

@trusktr

hey, I saw your issue at maxmaximov/getBoxQuads#1

I only wanted to tell you, I now created a polyfill for the getBoxQuads wich supports the transformations. Don't know if you still need it, only for info.

https://github.com/jogibear9988/getBoxQuadsPolyfill

@trusktr
Copy link
Member
trusktr commented Aug 24, 2024

@jogibear9988 this is awesome, thanks for making that!

I'm planning to add math functions to Lume and will include it when I do. Right now the Lume elements have position, rotation, scale, but there are no utilities for doing matrix math in Lume coordinates (which follows the DOMMatrix coordinate system), and the only math utilities are from Three.js for the underlying Three.js objects. Basically it is not a good experience if we have to bypass Lume's coordinate system because there are no math utilities, because then we have to switch mindset to Three's coordinate system and do math to align it with Lume's. Basically Lume similarly needs all those math utilities but for DOMMatrix/DOMPoint/etc instead of Three Matrix4/Vector3/etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0