I’m going to try the bottom-up approach. This is likely to be more fun for people who are more interested in creating beautiful images, and less compelling for people who want to create people and creatures that move and animate.
You can see the first lesson, which is very easy, by CLICKING HERE.
This lesson is really just to get you used to the idea of editing text in a computer program to change the appearance of something.
Thanks for the feedback on yesterday’s comment – very useful to know what the limitations on that concept are.
Any chance you could distinguish comments with color instead of case? (I say this totally understanding how dragging something like CodeMirror in complicates things…)
Done 🙂
If you’re talking about my on-line example code, I have a strong preference for getting learners used to editing with plain text when programming shaders, so they recognize the importance of the “//” comment delimiter. Otherwise they end up learning a particular IDE, rather than the shader language itself.
Interesting method, my main focus would be ways one could appeal to a younger audience. While the idea is good, the generation z digital natives of the world would need more shock and awe intro to shaders in my opinion. Keep up the good work.
Good point. We will get there soon enough. 🙂