Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Loader Improvements
See original GitHub issueI’m taking a crack at improving some of the loaders, making them a little more consistent in their usage, and then writing out the docs. I’ll post anything I need feedback on here.
First thing:
THREE.Loader has an addStatusElement method, which creates a DOM element that says “Loading …”. It doesn’t add it to the DOM, update it, or do anything with it. I was thinking about removing that method as it doesn’t appear to do anything, and is not used in the examples.
It seems that if there is any DOM loading interface it should go in THREE.LoadingManager. In fact maybe a visual interface should be a separate class that is only in the examples.
So my proposal is to remove that functionality, and if it gets put back in, put it into the examples. Thoughts?
Issue Analytics
- State:
- Created 10 years ago
- Comments:17 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
THREE.Loader no longer has any DOM/status management code, so I think this issue can be closed? If we want to do anything different with promises vs callbacks that could be opened in a new issue.
Hi all, One thing that springs to my mind regarding Promises, is that they allow for ES6 async / await style coding, which can help to simplify highly asynchronous code in many cases.