Sort of. I won't and can't prevent you from looking things up during the quiz, and I don't intend for you to feel you need to memorize the material. But try to do the reading first and then take the quiz.
Converting a scene graph (data structure of objects w/ geometry and material, and also light sources), and camera to pixels.
GUI is a standard acronym for Graphical User Interface. I assume the "dat" part is for data or some such.
Interesting question! Try it! I'll warn you, though, that (for performance reasons) Three.js doesn't check parameters for correctness, so all bets are off.
It means that when the value changes, to invoke (call) the handler function.
Awesome performance by the graphics card? All the scene stuff is in memory, but it does have to be re-transferred to the graphics card, which then has to render.
The bounding box is a dictionary parameter to the camera setup. (It's only purpose is to help set up the camera.) Adjust those six numbers.
It's up to you. You could have a keyboard control to toggle between day/night, to have objects appear and disappear, truly anything you want. For the next week or so, we'll be focussing on color and geometry, so those will be the things you'll want to affect for now.
Yes. That's how the dat.GUI
code is defined.
We'll get to that in about two weeks. See instance transform. See also Object3D.rotation() which is a method taking three arguments (rotation in radians around X-axis, Y-axis and Z-axis). See also rotateX() and friends.
We'll stick with dat.GUI, but if you find something you like better, you're welcome to do so. Share your discoveries!
I'm glad you're interested in how things work! I'm happy to talk with you about that in office hours, but our readings and class time will mostly focus on the application level.
This is a fantastic question and one I want to spend a little time on, because we'll see it again. It has to do with functions as arguments.