3 ms·

Why does the title have React.js when they are WebGL examples?

• zachrose 11y ago
  Something about making 3D primitives into a DOM-like hierarchy with update-able props: https://github.com/toxicFork/react-three-renderer#implementation-details https://github.com/toxicFork/react-three-renderer#implementa... Still wrapping my head around it.
  • vcarl 11y ago
    React has been ported a few times, React Native is the most well known. Since React is basically describing components as functions of props and state, what's returned doesn't have to be DOM.
• Silhouette 11y ago
  It's providing an interface/binding to that underlying functionality that fits into the React model of specifying a UI declaratively. Like almost any framework or library, React tends to be easiest to work with if you can follow its conventions. There is more friction if you want to do something outside its comfort zone, so this kind of bridge is potentially quite useful for anyone who does have a need for 3D visuals in their React-based app.
• morgante 11y ago
  Because it's demonstrating the binding of WebGL to React using this library: https://github.com/toxicFork/react-three-renderer/ https://github.com/toxicFork/react-three-renderer/
  • sktrdie 11y ago
    But where does React come into play?
    • alexwebb2 11y ago
      https://github.com/toxicFork/react-three-renderer/#usage https://github.com/toxicFork/react-three-renderer/#usage The library includes a lot of custom React components to represent the scene.