PART I
Warm-up
Reconnect with a useful idea before starting propose a host-neutral application contract. In one or two sentences, describe the input, output or host boundary from the previous exercise that this lesson builds on. If you are arriving directly, skim the worked example first; there is no locked prerequisite.
A rough note is enough. You can revise it after the example.
PART II
Instruction & guided example
Read application configuration as a request to a host
A host-neutral application contract describes user goals, supplied data, services, permissions, lifetime and evidence before choosing environment-specific integrations. The source’s Application constructor and app.ready callback are illustrative host inputs, not builtins supplied by this school. A Willow learner can reuse precise state reasoning while keeping proposed .ws and conceptual native services distinct from implemented .w.
The worked Application object names Workspace, requests a Dashboard window sized [1280,800] and registers an app.ready callback. Sample contract artifact: configuration input = application name/window/event response; host responsibilities = construct native application, provide window lifecycle, decide readiness; callback action = request the supplied console.log("Ready"); actual evidence = source inspection only. Registration is not readiness, and no ready event has been observed here.
A capitalized Application name does not make it a language primitive. Neither import app nor the object shape proves the constructor or console service is installed. Record those host inputs explicitly, including what readiness means before relying on it for later service use.
Worked reasoning and supplied artifact
import wuix.widget;
import app;
domain Workspace {
const application = Application({
name: "Workspace",
window: { title: "Dashboard", size: [1280, 800] },
events: {
"app.ready": fnc() -> void { console.log("Ready"); }
}
});
}Illustrative example from the proposed WillowScript design. The language and WUIX/WMATH/WDB/WAUDIO/WTMP services are not implemented in the supplied source. This site has no interpreter, VM or native host and does not execute or certify the snippet.
Walk through the example, one line at a time
import wuix.widget;Name the external module this script asks to use. Importing a name does not supply a host resource or grant its capability permissions.
import app;Name the external module this script asks to use. Importing a name does not supply a host resource or grant its capability permissions.
domain Workspace {Group related declarations under this named boundary. Read the nested declarations as the contents of that group.
const application = Application({Name a value that this example keeps stable. Inspect the right-hand side for the value or configuration being bound.
name: "Workspace",Read this key/value within its containing object. State which parent owns it and the narrow visible behavior it configures.
window: { title: "Dashboard", size: [1280, 800] },Read this key/value within its containing object. State which parent owns it and the narrow visible behavior it configures.
events: {Read this key/value within its containing object. State which parent owns it and the narrow visible behavior it configures.
"app.ready": fnc() -> void { console.log("Ready"); }This configuration value is a callback. Registration describes a response; the host contract determines when and with which context it is called.
}Close the nested block or value begun earlier. Match it to its opening boundary to keep the structure readable.
});Close the nested block or value begun earlier. Match it to its opening boundary to keep the structure readable.
}Close the nested block or value begun earlier. Match it to its opening boundary to keep the structure readable.
Try the guided change
Draw configuration → host construction → eventual readiness → callback request and mark every host-owned edge.
- Write the supplied inputs and initial state before following the example.
- Reconstruct each intermediate calculation or host decision, then compare with the worked artifact.
- Explain why the contrasting alternative fails before attempting the changed inputs in Part IV.
PART III
Take a breather
Step back after the guided example. Look away from the screen, stretch, or reread your prediction. This is an optional learning pause, not a timer or an assessment gate.
When you return, try to name the lesson’s key idea without copying its wording. If that feels difficult, return to Part II and trace one line rather than restarting the entire lesson.
PART IV
Independent practice
Project context: Independent WillowScript application. Build a small, understandable change around propose a host-neutral application contract.
Propose an expedition-kit planner application with a fixed window title and a readiness response. Supply a contract card explaining constructor, lifecycle and output-service inputs without claiming the application ran.
What to produce
A source-shaped application draft and an ownership/lifecycle contract with unobserved readiness status.
- State the intended behavior in a sentence before editing.
- Use only source-backed syntax and the host services whose contract you have been given.
- Record a normal case and a boundary or unavailable-resource case.
- Label hand predictions separately from anything actually measured in a supplied toolchain.
Syntax colors are a reading aid, not a compiler. The line you are editing stays uncolored until you move to a different line; capitalization is never changed. Drafts stay on this browser and code is not executed.
Need a hint?
The worked Application object names Workspace, requests a Dashboard window sized [1280,800] and registers an app.ready callback. Sample contract artifact: configuration input = application name/window/event response; host responsibilities = construct native application, provide window lifecycle, decide readiness; callback action = request the supplied console.log("Ready"); actual evidence = source inspection only. Registration is not readiness, and no ready event has been observed here.
A capitalized Application name does not make it a language primitive. Neither import app nor the object shape proves the constructor or console service is installed. Record those host inputs explicitly, including what readiness means before relying on it for later service use.
Original learning-path task and reference
Use your Willow knowledge to implement the .ws host integration, explaining which work remains native and which belongs in the script. In a rhythm-game audio editor, demonstrate propose a host-neutral application contract. Read the source-grounded example and predict its observable behavior before making changes. Include .ws source and a host-resource contract; compare at least one normal case and one edge case.
Where the original task needs a host API that is not supplied here, write the contract and predictions. Do not invent a runtime result.
PART V
Self-check
Use this check to notice what to revisit. It does not award a private course grade, block another page or claim to verify compiled code. Every answer has a learning explanation.
You may keep exploring even if you are unsure. Use the hint, compare the trace, and revise your explanation.
PART VI
Recap & small task
Bring the idea back to the mod feature you are building. A useful recap connects the mechanism to a decision you can make in your own code.
- Read application configuration as a request to a host
- Draw configuration → host construction → eventual readiness → callback request and mark every host-owned edge.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Draw configuration → host construction → eventual readiness → callback request and mark every host-owned edge.
This marks your personal practice record only. It is not a certification or an official workspace assessment.