I had an idea just now whilst reading through some tutorials with broken examples online. It feels like ‘wasted’ code/work as i’m sure with the correct tweaking these examples and code could be made to work again. Obviously asking people to continuously update their tutorials is unreasonable… BUT…
If you could ‘tag’ a three.js file as learning material. And then from within three.js core code, trigger a noob friendly information screen explaining why they’re seeing a black screen - something like:
This example has been tagged as learning material and did not run correctly.
Why did this happen?
[Insert explanation about revision system and how small syntax changes could break the whole thing]
Old revisions of three.js are using incorrect/dated syntax. Please see [link to relevant update log] to get this code working again.
Visit discourse.threejs.org for further information.
It took me a little while to get to grips with why this was happening at all. So i just wonder if something as simple as this could just encourage new learners to push through that initial fear of seeing a tutorial with a broken example. The reality is its not that broken, but a black screen says the opposite.
I don’t know enough about three to really make out like my idea is feasible or not. But it seemed like a good idea and a solution to a problem without adding tonnes work? I might be wrong.