<h3 dir="auto">Documentation linking to existing examples?</h3>
<p dir="auto">I'm slowly working on some of the documentation and I'm trying to figure out how to add some examples here and there in the docs. I'd like to not duplicate work that's already been done. I believe I will link to examples using relative links where they are pertinent in the API. I don't believe I've seen that done yet. It might be nice to also link to handy external examples.</p>
<h3 dir="auto">Embedded live examples</h3>
<p dir="auto">I'm not sure I'm going to go this next route, but I was wondering if inline examples would be completely out of the question. Specifically some tweakable examples with the various mesh materials I believe would be quite helpful.</p>
<h3 dir="auto">/src code vs /examples code</h3>
<p dir="auto">My next question is regarding the examples code base vs. the src code base. What's the reasoning behind the split between some of the code? A lot of the code in examples is quite handy and I feel like it should be documented. There's no structure in place for that as of yet.</p>
<p dir="auto">There are a few things which geometry.clone() doesn't copy a reference to, which it should.</p>
<p dir="auto">.bones<br>
.skinWeights<br>
.skinIndices<br>
.animations<br>
.animation</p>
<p dir="auto">are all left without references to the original, which leads to skinning being broken unless the references to those are manually copied. I think references should be passed as it's less confusing, but I don't think they should be deep copies, or this would lead to mostly wasted memory.</p>