I see. Well quite some work went into upgrading the globe.js to Three.js rev 56 (API changes and debugging related errors) and the integration stuff (creating the geo data) under the hood. Plus using particles instead of the cubes (which was rather easy). So although it still has definitely a lot from your version (globe and three.js) it's definitely not just a cheap and quick copy for ripping off credits ;) That's why I appreciated the comment. Consider a big part of the credit as yours :)
Just a side-node: the API docs were the biggest obstacle in the whole process. W.r.t to platform usage I think this would be one of the top prio things to get even more people using Three.js.
Comments
I see. Well quite some work went into upgrading the globe.js to Three.js rev 56 (API changes and debugging related errors) and the integration stuff (creating the geo data) under the hood. Plus using particles instead of the cubes (which was rather easy). So although it still has definitely a lot from your version (globe and three.js) it's definitely not just a cheap and quick copy for ripping off credits ;) That's why I appreciated the comment. Consider a big part of the credit as yours :)
Just a side-node: the API docs were the biggest obstacle in the whole process. W.r.t to platform usage I think this would be one of the top prio things to get even more people using Three.js.
Yup. Working on that... also need to update WebGL Globe so you don't have to :)