package locations about three.hx HOT 3 CLOSED

I am following the structure of the three.js library and think i will keep it this way.
Someone could flatten the structure with typedefs or --remap if that's preferable.

from three.hx.

Sure, just saying you're kind of fragmenting the use of threejs and haxe.. also why are didn't you just contribute to the externs that are already on haxelib?

from three.hx.

Also I doing think you're correct when you say you're following the structure of three.js, when importing pretty much any class it's THREE.SomeClass

from three.hx.