Introduction to Event-Driven Programming

Active learning works well for this topic because event-driven programming requires students to shift from writing linear code to visualizing interactions between objects and events. Hands-on activities help them see how real-world systems respond to inputs, which makes abstract concepts like event handlers and listeners more concrete.

• JC 2
• Computing
• 3 activities
• 15 min–30 min

Learning Objectives

1. Identify the core components of an event-driven programming model.
2. Explain how user interactions are translated into program events.
3. Design a simple graphical user interface that responds to mouse clicks.
4. Compare event-driven programming with sequential or procedural programming paradigms.
5. Create a basic program that executes specific functions based on keyboard input.

Think-Pair-Share

⏱ 15 min·Pairs

Think-Pair-Share: The Blueprint vs. The House

Students identify a real-world object (e.g., an EZ-Link card) and list its attributes and methods. They then compare their lists in pairs to decide which data should be 'private' and which 'public' to ensure security and functionality.

Prepare & details

What is an 'event' in programming?

Facilitation Tip: During Think-Pair-Share, provide each pair with a printout of a simple class definition and a matching object so students physically match the template to its instance.

Setup: Standard classroom seating; students turn to a neighbor

Materials: Discussion prompt (projected or printed), Optional: recording sheet for pairs

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Inquiry Circle

⏱ 30 min·Small Groups

Inquiry Circle: Object Modeling

Small groups are given a scenario, such as a library management system. They must draw a class diagram on a whiteboard, defining the attributes and methods for 'Book', 'Member', and 'Loan' objects, then explain their design to another group.

Prepare & details

How do interactive apps and games respond to what a user does?

Facilitation Tip: For Collaborative Investigation, assign each group a different real-world scenario to model, such as a traffic light or a coffee machine, to ensure diverse examples.

Setup: Groups at tables with access to source materials

Materials: Source material collection, Inquiry cycle worksheet, Question generation protocol, Findings presentation template

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

Peer Teaching

⏱ 25 min·Pairs

Peer Teaching: Encapsulation Defense

One student writes a class with public attributes. Their partner must 'hack' the object by setting invalid values (e.g., a negative age). The first student then refactors the code using private attributes and setter methods with validation logic to 'defend' the data.

Prepare & details

Design a simple program that reacts to a button click.

Facilitation Tip: In Peer Teaching, give students a flawed encapsulation example to defend, forcing them to identify and explain why certain methods should be private.

Setup: Presentation area at front, or multiple teaching stations

Materials: Topic assignment cards, Lesson planning template, Peer feedback form, Visual aid supplies

• Understand
• Apply
• Analyze
• Create
• Self-Management
• Relationship Skills

Teaching This Topic

Start by grounding the concept in familiar examples, like a remote control, where students can see how pressing a button (an event) triggers an action. Avoid overwhelming them with syntax first; focus on the mindset shift from procedural to event-driven thinking. Research shows that students grasp encapsulation better when they see how private methods reduce complexity in large systems.

What to Expect

Students will demonstrate understanding by creating a class that models a real-world object, defining private methods for internal logic, and writing event handlers to respond to user actions. They should explain the difference between a class and an object and justify why encapsulation improves program design.

Watch Out for These Misconceptions

Common Misconception

During Think-Pair-Share, watch for students who confuse the class definition with the object instance.

What to Teach Instead

Have students physically separate the class definition (the blueprint) from the object creation line, then explain how the same class can produce many distinct objects.

Common Misconception

During Peer Teaching: Encapsulation Defense, watch for students who argue that all methods should be public for flexibility.

What to Teach Instead

Guide them to examine the provided flawed example, then highlight how private methods simplify the interface by hiding unnecessary details.

Assessment Ideas

Exit Ticket

After Think-Pair-Share, provide students with a short code snippet showing a button class and its object. Ask them to write: 1) the event name, 2) the event handler, and 3) the expected output when the button is clicked.

Discussion Prompt

During Collaborative Investigation, ask each group to present their modeled object and explain which events it should handle and why. Listen for specific references to mouse or keyboard inputs and the actions they trigger.

Quick Check

During Collaborative Investigation, circulate the room and ask each group to demonstrate how they attached an event listener to their object. Provide immediate feedback on correct syntax and logic, such as missing event names or incorrect handler placement.

Extensions & Scaffolding

• Challenge: Ask students to design a class with nested event handlers, such as a game where a key press triggers a secondary event like a power-up activation.
• Scaffolding: Provide a partially completed class with missing event handlers and have students fill in the blanks to respond to a mouse click or keyboard input.
• Deeper exploration: Introduce asynchronous events, such as timers or network responses, and discuss how event-driven programming handles them differently than procedural code.

Key Vocabulary

Event	A signal indicating that something has happened, such as a user clicking a button or pressing a key.
Event Handler	A function or method that is executed in response to a specific event occurring.
Event Loop	A programming construct that continuously checks for and dispatches events to appropriate handlers.
Callback Function	A function passed into another function as an argument, which is then invoked inside the outer function to complete a routine or action.
GUI (Graphical User Interface)	A visual way of interacting with a computer using windows, icons, and menus, often involving event-driven interactions.