package locations

[peteshand]

While technically not an bug, I've just noticed that the package structure is quite different between these externs and the ones at https://lib.haxe.org/p/threejs/ and threejs in general.

There are a few haxe libs out there that have a dependency on the other threejs externs, so it might be a good idea to follow the same package structure so they can be easily substituted these new externs.

[tong]

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.

[peteshand]

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?

[peteshand]

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