Compose text and button components — Discover and trace

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

Separate a button label from its action

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.

Host contract: a Continue button stores a no-argument void callback; one delivered click requests navigator.open("dashboard"). The navigator service is an exercise-host dependency with a separate permission check.

Worked reasoning: Configuration creation stores the response without navigation. A delivered click invokes it and requests dashboard. An allowed request changes the route; a denial leaves the current route unchanged.

Failed alternative: Calling navigator.open while constructing text or configuration navigates before the user action and does not install a deferred response.

Worked reasoning and supplied artifact

// Proposed callback/configuration syntax
const button = { text: "Continue", events: {
    click: fnc() -> void { navigator.open("dashboard"); }
}};
// create -> no route change; click + allow -> dashboard; click + deny -> unchanged

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 callback/configuration syntax
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
const button = { text: "Continue", events: {
Name a value that this example keeps stable. Inspect the right-hand side for the value or configuration being bound.
click: fnc() -> void { navigator.open("dashboard"); }
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.
// create -> no route change; click + allow -> dashboard; click + deny -> unchanged
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.

Design Review order routing to order-summary. Supply create/no-click, allowed-click and denied-click predictions.

What to produce

A button configuration plus a three-outcome action timeline.

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?

The callback represents deferred work; delivered user action is the trigger in this host contract.

Calling navigator.open while constructing text or configuration navigates before the user action and does not install a deferred response.

Original learning-path task and reference

In a racing checkpoint editor, demonstrate compose text and button components. 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.

When should navigation be requested?When the host delivers clickWhen the label is constructedWhenever the source is highlighted

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.

Separate a button label from its action
Design Review order routing to order-summary. Supply create/no-click, allowed-click and denied-click predictions.
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Distinguish stored response, delivered click and permitted navigation.

Your recap

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