WillowScript (.ws) is a proposed, not-yet-implemented language. Examples and library integrations here are illustrative design exercises, not verified runnable programs.
Handle an explicit window-close event
Being able to name an API does not mean the script is allowed to use every resource behind it. Exposure asks which API is visible to the script. Capability permission asks which operations and resources the host authorizes for this particular execution.
- 1→
Handle an explicit window-close event — Discover and trace
Make a prediction before touching the example.
Open practice - 2→
Handle an explicit window-close event — Build the smallest useful slice
Change one useful behavior while keeping the contract small.
Open practice - 3→
Handle an explicit window-close event — Change one requirement
Translate one new mod requirement into a deliberate change.
Open practice - 4→
Handle an explicit window-close event — Boundary detective
Find a case the simplest success path does not cover.
Open practice - 5→
Handle an explicit window-close event — Flash-check repair
Use a plausible mistake to show that you understand the mechanism.
Open practice - 6→
Handle an explicit window-close event — Connect the previous skills
Connect this idea with a previously learned responsibility.
Open practice - 7→
Handle an explicit window-close event — Review and demonstrate
Collect a useful learning record without pretending the code was executed.
Open practice - 8→
Module project — Support request workflow
Turn the section work into one reviewable mod feature.
Open practice
