Great to announce that start of v3.x.x development!
Short FAQ:
When? Probably till the end of this (2018) year
Who? @sasha240100 @hirako2000 and everyone who wants to join (you can ask in this issue comments & propose your changes)
What it will be? Yep, the most interesting question, I'll write down below.
Proposed features
- New Three.js version in the core of the library + Support for further version updates
- Components automation. Three.js always adds new types of geometries, lights, meshes and so on and currently we handle them manually. We would probably write a code that will parse three.js geometries/lights/etc and make components from them.
- Better
WHS.Loop I really like that we split requestAnimationFrame into loops, but I think we can do that an even better way [API is currently under discussion].
- New (simplified) Module lifecycle. Same. Modules is a strong part of whs framework, but their complexity is whs weakness, and we'll try to make them more human-readable and better-piped way.
- Support for new Three.js features.
THREE.WebGL2Renderer support
- (soon...)
- Better documentation. (more details soon...)
Feel free to add your suggestions to the future release in this issue comments
Subtasks:
Version:
Issue type:
Tested on:
Desktop
Android
IOS
Great to announce that start of
v3.x.xdevelopment!Short FAQ:
When?Probably till the end of this (2018) yearWho?@sasha240100 @hirako2000 and everyone who wants to join (you can ask in this issue comments & propose your changes)What it will be?Yep, the most interesting question, I'll write down below.Proposed features
WHS.LoopI really like that we split requestAnimationFrame into loops, but I think we can do that an even better way [API is currently under discussion].THREE.WebGL2RenderersupportSubtasks:
Version:
Issue type:
Tested on:
Desktop
Android
IOS