- Without using "LerpSphere" (commenting
it out), do the following with "SphereMatrix". We
should only be seeing balls changing visibility, position, radius,
colors, and other gross attributes at this point. Changing cv's
will come later. If any of these problems appear too difficult,
skip it. If you have a better idea, do that idea instead. In
other words, have fun with "SphereMatrix". For some
of these problems, you may write your own procedures that is
based on "SphereMatrix" architecture instead of just
modifying it-- procedures that modify the spheres after they've
been drawn.
-
-
- (1) "SphereMatrix(
string $name )" is designed to only create an 8 x 6
sphere matrix. Redesign it so that it can generate any size
sphere matrix. It should now become "SphereMatrix( string
$name, int $ncols, int $nrows )". Test it with various
numbers.
-
-
- (2) Create a procedure that
changes the visibility attribute of each sphere after they've
been drawn. Give the illusion that only one sphere is there
and that it moves through all the matrix positions. Make it
dependent on the frame number and link it to an expression.
-
-
- (3) Create a 3D version of
"SphereMatrix". Call it "SphereCube".
-
-
- (4) Modify "SphereMatrix"
so that it modifies other sphere attributes like "radius".
In other words, the balls may interpolate through various sizes.
-
-
- (5) Change the generated
ball positions so they form a wavy matrix-- like a flag waving.
(e.g., put a sine() procedure on the "y" direction
during generation, or write a procedure that modifies sphere
positions using "move -r" after the matrix has been
drawn.)
-
-
- (6) Put a random element
into the sphere ball generation.
-
-
- (7) Change sphere colors
so that spheres have a different color at different parts of
the matrix.
-
-
- (8) Do a combination of the
problems above. In other words, make only one sphere visible
and make it change sizes and colors as it moves through matrix
positions using the timeline.