Compose text and button components — Change one requirement

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.

Recall note

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

PART II

Instruction & guided example

Adapt the label and target together

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.

The original Continue control routes to dashboard. The new requirement is Review invoice and route invoice-review. Host navigation permissions allow invoice-review but deny dashboard in this workflow.

Worked reasoning: Changing both label and destination aligns visible intent with requested behavior. Under the new contract a click can reach invoice-review. Changing only the label still requests denied dashboard and misleads the user.

Failed alternative: A cosmetic rename leaves the old navigation request unchanged, so the user sees a new promise with the wrong effect.

Worked reasoning and supplied artifact

// Proposed configuration fragment
{ text: "Review invoice", events: {
    click: fnc() -> void { navigator.open("invoice-review"); }
}}
// Intent:invoice review;request:invoice-review;permission:allow

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

// Proposed configuration fragment
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
{ text: "Review invoice", events: {
Read this key/value within its containing object. State which parent owns it and the narrow visible behavior it configures.
click: fnc() -> void { navigator.open("invoice-review"); }
This configuration value is a callback. Registration describes a response; the host contract determines when and with which context it is called.
}}
Read this statement in its surrounding contract. Identify which value or host operation it contributes; do not infer an undocumented API.
// Intent:invoice review;request:invoice-review;permission:allow
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.

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.

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

Adapt a Dashboard button to Inspect shipment with target shipment-inspector. Include one test that distinguishes a label-only edit from a complete change.

What to produce

A label/route/permission contract and discriminating click case.

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?

User intent and requested destination are separate fields that both changed in this requirement.

A cosmetic rename leaves the old navigation request unchanged, so the user sees a new promise with the wrong effect.

Original learning-path task and reference

In a rhythm-game audio editor, demonstrate compose text and button components. Adapt the task to a second host-neutral application context without changing the imported API contract. 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 edit fulfills the changed requirement?Change label and routeChange label onlyKeep dashboard because imports match

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.

Adapt the label and target together
Adapt a Dashboard button to Inspect shipment with target shipment-inspector. Include one test that distinguishes a label-only edit from a complete change.
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Compare the visible verb with the route requested by its response.

Your recap

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