PART I
Warm-up
Reconnect with a useful idea before starting review your planning-screen 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
Connect the planning artifact to a display boundary
The output of a planning exercise may be a screen description, while the native service is responsible for presentation. Integration means tracing that artifact into the supplied host operation, not replacing it with an invented browser DOM workflow.
The worked screen’s single component says Workshop plan: inspect then repair. Its sample integration map lists producer = declarative screen; consumer = wuix.mount; transferred value = screen; target = main; trigger = host invokes show; unresolved = target readiness and presentation result. These entries identify exactly where local description stops and host behavior begins.
A successful paper map does not prove that show was invoked or that a visible screen appeared. Do not substitute document.createElement or HTML button APIs for WUIX. If a host trigger is absent, record the missing trigger contract rather than fabricating one.
Worked reasoning and supplied artifact
import wuix.widget.button;
import wuix.layout;
domain Login {
const screen = {
layout: { type: "column", padding: [24,32], gap: 16 },
components: [{ type: "text", value: "Workshop plan: inspect then repair" }]
};
fnc show() -> void {
wuix.mount("main", screen);
}
}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.button;Name the external module this script asks to use. Importing a name does not supply a host resource or grant its capability permissions.
import wuix.layout;Name the external module this script asks to use. Importing a name does not supply a host resource or grant its capability permissions.
domain Login {Group related declarations under this named boundary. Read the nested declarations as the contents of that group.
const screen = {Name a value that this example keeps stable. Inspect the right-hand side for the value or configuration being bound.
layout: { type: "column", padding: [24,32], gap: 16 },Read this key/value within its containing object. State which parent owns it and the narrow visible behavior it configures.
components: [{ type: "text", value: "Workshop plan: inspect then repair" }]Read this key/value within its containing object. State which parent owns it and the narrow visible behavior it configures.
};Close the nested block or value begun earlier. Match it to its opening boundary to keep the structure readable.
fnc show() -> void {Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
wuix.mount("main", screen);Ask the supplied native UI service to mount the declared screen at the named host target. Confirm the target exists in the exercise contract.
}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
Fill the producer/consumer map from the source and draw the host trigger as an external precondition.
- 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: Accessible welcome screen. Build a small, understandable change around review your planning-screen contract.
Connect a fixed route-planning screen to the main target using the source-named mount form. Explain who owns the content, who supplies the target and what evidence would be needed to claim actual presentation.
What to produce
An integration map, a source draft and a separate evidence-needed statement for real rendering.
- 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 screen’s single component says Workshop plan: inspect then repair. Its sample integration map lists producer = declarative screen; consumer = wuix.mount; transferred value = screen; target = main; trigger = host invokes show; unresolved = target readiness and presentation result. These entries identify exactly where local description stops and host behavior begins.
A successful paper map does not prove that show was invoked or that a visible screen appeared. Do not substitute document.createElement or HTML button APIs for WUIX. If a host trigger is absent, record the missing trigger contract rather than fabricating one.
Original learning-path task and reference
In a small-shop operations tool, demonstrate review your planning-screen contract. Integrate this section with the preceding section’s artifact; identify inputs, outputs, and host capabilities. Include .ws source and a host-resource contract; compare at least one normal case and one edge case.
import wuix.widget.button;
import wuix.layout;
domain Login {
const screen = {
layout: { type: "column", padding: [24, 32], gap: 16 },
components: [{ type: "text", value: "Welcome back" }]
};
fnc show() -> void {
wuix.mount("main", screen);
}
}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.
- Connect the planning artifact to a display boundary
- The output of a planning exercise may be a screen description, while the native service is responsible for presentation. Integration means tracing that artifact into the supplied host operation, not replacing it with an invented browser DOM workflow.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Name the transferred value without calling it a browser element.
This marks your personal practice record only. It is not a certification or an official workspace assessment.