Term | Definition |
Bugs | Problems or errors in code that either stop the program from running or do not allow the program to accomplish the intended goal. |
Code Editor | Where the programmer adds and edits code. |
Coding | Using a programming language to give instructions that are understandable to the computer. |
Commands | Instructions that the computer follows that makes action on the stage occur. A series of these make up a program. |
Coordinate Plane | This is a flat area defined by an x-axis that runs horizontally (side to side) and a y-axis the runs vertically (up and down). |
Debugging | The process where the programmer reviews the code and fixes problems and errors. |
Origin | At location (0,0) on the coordinate plane, this is where the x and y axis cross. In Codesters, this is located at the center of the stage. |
Pixels | The unit of measurement on the stage. |
Point | Locations on the coordinate plane; described by a pair of coordinates (X,Y). |
Programming | Giving instructions to a computer. |
Python | A programming language; the programing language we are learning and using in Codesters. |
Sprite | A character, shape, or other object that we add to our scene/stage. |
Stage | Where the results (or scene) of your program appears. |
Toolkit | Holds tools and blocks of code that can be used (dragged into your code editor) to build your program. |
X- Coordinate | A location on the coordinate plane that determines how far to move horizontally. The first number in an ordered pair. |
Y- Coordinate | A location on the coordinate plane that determines how far to move vertically. The second number in an ordered pair. |