Compose text and button components — Boundary detective

PART I

Warm-up

Reconnect with a useful idea before starting compose text and button components. 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

Bound repeated clicks with a stated policy

Text communicates state and a button requests an action. Their composition needs a semantic contract: label, event, target, permission, repeated action and failure response. Native controls do not remove those responsibilities. Callback values and object configuration are proposed source forms, not executed code here.

A host report request takes four seconds. The exercise policy allows only one in-flight request per owner. At t0 a click starts R1; a second click arrives at t1; R1 succeeds at t4.

Worked reasoning: Track busy false ->true on R1 start. The t1 click is ignored with status Preparing; no R2 starts. At t4 success applies to the owner and busy becomes false. This is a supplied policy, not an assumed button builtin.

Failed alternative: Assuming native buttons automatically deduplicate starts R2 and may create duplicate reports under a host with no such guarantee.

Worked reasoning and supplied artifact

t0:click,busy=false ->startR1,busy=true
t1:click,busy=true ->no new request
t4:R1 success ->show report,busy=false
Request count:1

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.

Try the guided change

Reconstruct the supplied worked case first: list its inputs, intermediate decisions and final artifact. Compare each row with the explanation and identify exactly where the rejected alternative fails. Then use the changed inputs in Part IV for independent work.

• 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: Operations dashboard. Build a small, understandable change around compose text and button components.

Trace clicks t0, t2, t6 with completion at t5 under the same rule. Identify which clicks may start work.

What to produce

A click/busy/request ledger plus a documented interaction policy.

• 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.

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);
    }
}

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.

• Bound repeated clicks with a stated policy
• Trace clicks t0, t2, t6 with completion at t5 under the same rule. Identify which clicks may start work.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Write the busy state before each click rather than counting click events as requests.

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