Firtina Ozbalikci

Regarding lower case components being html perhaps we could extend the definitions or something to accept custom "native types", I think that would be awesome for prop type verification on...

I think things would need to be context sensitive somehow as new renderers emerge. Could do an annotation to a file or the render function for example to specify what...

That's a bad component that should be split in half and deserves multiple warnings ;) On Fri, Nov 18, 2016, 11:48 jugglingcats [email protected] wrote: > I don't understand very much...

Cool solutions :) I would prefer a comment / `.d.ts` based solution even if it takes more work because I am against overheads in general. However, there are ways to...

Hi @lepus2 Before this project can be used for react native, WebGL and threeJS may need to be implemented for react native. I am sure some people are working on...

We could write a wrapper for the importers, or use an importer to populate a mesh instead?

> unnecessary updates by injecting geometry into an existing mesh component Well, essentially it's similar to: ``` var geom = new THREE.Geometry(); geom.vertices = meshData.vertices; geom.faces = meshData.faces; ... mesh.geometry...

@zhuber yes, this is cool! :D I had tried a bit of it to have it "work natively" for the fiber implementation but an external package feels best.

For now I'd do something like this: ``` jsx componentDidMount(){ const group = this.refs.group; // geometry var geometry = new THREE.BoxGeometry( 100, 100, 100, 4, 4, 4 ); // materials...

Hi @milanzigmond [a community member is working on a potential implementation of multi materials](https://gitter.im/toxicFork/react-three-renderer?at=59a7bb1cb16f264642ee195b), but not sure when that would be completed and merged. For now you can use [componentDidUpdate](https://facebook.github.io/react/docs/react-component.html#componentdidupdate)...