Review your planning-screen contract — Discover and trace

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.

Recall note

A rough note is enough. You can revise it after the example.

PART II

Instruction & guided example

Review a screen from configuration to host mount

A screen contract has two layers: the declarative content/layout and the host operation that presents it. Read both before judging whether a welcome feature is complete. WUIX is a proposed native UI service; the object literal and APIs here illustrate the source design, not a parser-verified browser component.

The configuration requests a column, padding [24,32], gap 16 and one text component whose value is Welcome back. show passes that same screen object and target main to wuix.mount. A complete sample contract card is: purpose = welcome returning users; content = Welcome back; layout = column; target = main; precondition = host supplies WUIX and that target; evidence = paper inspection, no mount observed.

An import names a dependency but does not prove target availability or permission. Likewise, a const screen declaration does not display anything by itself. If show is never called by the host, the shown source only describes content and a possible activation path. The host must also define when and how it invokes show.

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: "Welcome back" }]
    };
    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: "Welcome back" }]
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

Draw configuration → show → mount request → host target. Put the host preconditions beneath the final arrow rather than inside the object keys.

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.

Prediction or guided notes

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.

Your drafts remain here. Continue whenever you are ready.

PART IV

Independent practice

Project context: Accessible welcome screen. Build a small, understandable change around review your planning-screen contract.

Review a workshop planning screen greeting the user with Today’s workshop. Supply a contract card, identify all host inputs, and explain what can be inspected without running the proposed service.

What to produce

Source annotation, a five-field contract card and a distinction between declared screen and observed presentation.

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.

Your .ws practice draft

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?

Original learning-path task and reference

In a strategy simulation analytics tool, demonstrate review your planning-screen 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.

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.

Which operation requests presentation at the main target?wuix.mount("main", screen)The word const aloneThe padding array alone

Explain a normal or boundary case

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.

Review a screen from configuration to host mount
A screen contract has two layers: the declarative content/layout and the host operation that presents it. Read both before judging whether a welcome feature is complete. WUIX is a proposed native UI service; the object literal and APIs here illustrate the source design, not a parser-verified browser component.
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Name one host precondition the screen object cannot establish.

Your recap

This marks your personal practice record only. It is not a certification or an official workspace assessment.