How can we improve documentation?

https://threejs.org/docs/index.html?q=BoxGeometry#api/en/geometries/BoxGeometry
https://threejs.org/docs/index.html?q=BoxGeometry#api/en/geometries/BoxBufferGeometry

One of these is depreciated, which is it?

Depreciated is for cars.
Deprecated is for API’s.

BoxGeometry was once replaced by BoxBufferGeometry, (thus BoxGeometry was deprecated) then BoxBufferGeometry replaced BoxGeometry, and BoxBufferGeometry was deprecated, and BoxGeometry was replaced by BoxBufferGeometry, and un-deprecated. It was a weird time. We have scars.

Now we pretend like the original Geometry class never existed, but it still pops up now and then like a zombie.

There’s good information in the docs, but they are getting pretty creaky. The search is weird/busted in the examples, and in the API docs. They really need some modernization / love. :stuck_out_tongue:

According to the above .traverse is a method for scene. I can’t find it in the documentation.

Ha, I never noticed. Now I don’t have to explain how novice I am.

Thanks for the reply. I’m struggling with the docs as I learn. Yes, the search doesn’t work well.

1 Like

It’s inherited from Object3D (you can see the inheritance chain at the top of every docs page.)