On Oliver's Easel

Show Me a side menu for unpacking this page into its structural elements
Hide
× Guide
Plot points What just happened What is happening What will happen
Crew Composer: Oliver Composer: Val Content-provider: Miguel Content-provider: Vanessa Inter and Re-Actor: Lucia
Requirements
Overview
List Assets
Common Questions

Working interface:

What's happening here?
Vertex423 made an animation using Scratch!

Oliver says: 'Cool! but I want to make my avatar.'

Val says: This is an example of a walk cycle. It was made by using 24 different costumes for the monster; 12 costumes for the stick figure; 4 costumes for the Pikachu character.

How was this made? screenshot of the Scratch Script page of the animation program Pass the pseudocode, please

Care to add some dialogue?

Pikachu yells: "Aaaaaagggghhhhhhhhhh...."
Describe how you'd make this here.
Ask me something directly command-line interface (like console or git)
Search your project database

drag and drop where you think this animation would be found in this story here's an example
If you had to make up one thing for a character that's already in this animation to do instead of what it's doing - what would that be?
Current Notes and open-Questions for Collaborators:

Ian - I would be tempted to put all of the following in the 'exposition' element and just make most of the textContent display:none, but I'm guessing that's not the way UX would present the info. Thoughts?

What's happening here?
Vertex423 made an animation using Scratch!
Oliver says: ____________________
Val says: This is an example of a walk cycle. It was made by using 24 different costumes for the monster; 12 costumes for the stick figure; 4 costumes for the Pikachu character. Wikipedia says: In animation, a walk cycle is a series of frames or illustrations drawn in sequence that loop to create an animation of a walking character.
How was this made?
The Composer probably traced some keyframes from videos he found online.
    Scratch
  1. There's a green flag on the screen that waits to be pushed.
  2. Then inside of a forever function,
    1. the browser first waits for 0.05 seconds,
    2. then replaces the sprite's costume with its next costume in that sprite's list of Costumes;
    3. then it does the same thing again - it waits for 0.05 seconds, then changes the sprite's costume to the next costume.
    4. And again...forever...(theoretically)
Pass the pseudocode, please
  1. Find the DOM element that has a green flag (it's probably an <img> or <svg> tag
  2. Create a javascript representation of that element. Here, let's name it 'greenFlag'
  3. Add an event listener onto that element named 'greenFlag' that listens for the InterActor to click on the mouse. When the InterActor clicks on the mouse, a function will run.
  4. This function is an infinite loop (WARNING: don't write infinite loops in your own programs that have to run in the browser because the browser will either crash or just stop your program.)
  5. Create a method that calls a second function after 0.05 seconds
  6. This second function looks at a list of images (costumes) for
  7. There is already an image for