Initialize the renderer.
The width of the screen
The height of the screen
The ID of the DOM element into which we will render
True if debug outlines should be drawn
Optional mostThe most recently-taken screenshot
The pixi application object is responsible for drawing onto a canvas
Is someone requesting that a new screenshot be taken?
The "time" in milliseconds, where 0 is when the game started
Add an actor (physics+image) to the next frame
The AppearanceComponent for the actor
The rigidBody of the actor
The sprite, from appearance
The camera that determines which actors to show, and where
The Z index of the sprite
Where is this being drawn (WORLD, OVERLAY, or HUD)?
Add a filled sprite (a Pixi Graphic) to the main container
The filled sprite to draw
The rigid body that accompanies the filled sprite
The graphic context
The camera (and by extension, the world)
The Z index of the sprite
Where is this being drawn (WORLD, OVERLAY, or HUD)?
Add a filter to the whole container
The filter to add
Where to put the filter (WORLD, OVERLAY, HUD, BACKGROUND, or FOREGROUND)
Add a Picture to the next frame. Note that pictures are never rotated or offset, because we only use this for Parallax pictures (which have no rigid body, and hence no rotation).
The AppearanceComponent for the actor
The sprite, from appearance
The camera that determines which actors to show, and where
Should this go in the foreground (true) or background (false)?
Add text to the next frame
The text object to display
The rigidBody of the actor
The camera that determines which text to show, and where
Should we center the text at its x/y coordinate?
The Z index of the sprite
Where is this being drawn (WORLD, OVERLAY, or HUD)?
Add a filter to one of the z indices.
The filter to add
The z index on which to add the filter
Where to put the filter (WORLD, OVERLAY, or HUD)
RenderDevice is a wrapper around the PIXI Application object. It initializes the render loop, which fires at a regular interval to tell the game to advance the simulation by some number of milliseconds. Doing this many times per second is what makes our game work :)
TODO: Pixi prefers when sprites are not removed and re-added to containers on each tick. It also has features like "interaction" that can be disabled. There's a fair bit of optimization opportunity.