# Input / Output ## Text-Driven Input Your program will take input from the user in the form of typed answers, or *text*. This is the simplest method of gathering input from the user. Some languages allow input on the command-line or wait for the user to type a response, some do both. This is text-based input where the user utilizes the keyboard to enter data. Javascript utilizes the [**`prompt()`**](/unit-2/input-output/prompt-alert-confirm.md#prompt) command for this (not available in Node.js). ## Event-Driven Input User input can also be collected with the click of a mouse, a voice command, or a selection from options. We call these actions **`Events`**. Essentially, your program "listens" for events and when one happens, it reacts accordingly. **Later in the course**, if we progress well enough, we can learn how to deal with a user clicking a button or selecting something on a webpage. This would take us away from the console and allow us to develop a front-end or graphical user interface (GUI). Hopefully more on that later. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://cs.brash.ca/unit-2/input-output.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.