Build the Beginner final project — Connect the previous skills

PART I

Warm-up

Reconnect with a useful idea before starting build the beginner final project. 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

Connect prior calculation skills without inventing interpolation

A welcome project may want to show a calculated value, but a correct integer helper does not establish a text-conversion or interpolation API. Keep arithmetic evidence and UI integration contracts separate until the source supplies the bridge.

Suppose the workshop has 12 planned steps and 5 completed. remaining(12,5) predicts 7 by subtraction. The desired UI message is 7 steps remain, but the demonstrated text component holds a fixed string. A complete sample integration plan says: arithmetic result = i32 7; desired content = that count in readable text; missing contract = conversion/binding mechanism; safe current draft = fixed orientation text, no dynamic-display claim.

Do not insert JavaScript template literals or call an invented toString method as if either were verified WillowScript. A concrete missing-contract note is progress: it names exactly what the future host or language design must provide before this integration can be implemented honestly.

Worked reasoning and supplied artifact

fnc remaining(total: i32, completed: i32) -> i32 {
    return total - completed;
}
// Hand case: remaining(12,5) predicts 7.
// UI goal: present that count; conversion/binding contract is not supplied.

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

fnc remaining(total: i32, completed: i32) -> i32 {
Read the function name, its parameter names/types and the result type after ->. This is the contract the body must satisfy.
return total - completed;
Evaluate the following expression using the current values, then send its result to the caller. Explain the value; do not confuse it with printed output.
}
Close the nested block or value begun earlier. Match it to its opening boundary to keep the structure readable.
// Hand case: remaining(12,5) predicts 7.
This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.
// UI goal: present that count; conversion/binding contract is not supplied.
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

Trace the arithmetic and write the desired message as a product expectation, then name the missing conversion boundary.

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 build the beginner final project.

Your workshop has 9 materials planned and 4 prepared. Calculate the remainder, describe the desired welcome message, and write an integration contract that avoids claiming unsupported interpolation or execution.

What to produce

Arithmetic trace 9-4=5, desired message text and an explicitly unresolved dynamic-binding contract.

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?

Suppose the workshop has 12 planned steps and 5 completed. remaining(12,5) predicts 7 by subtraction. The desired UI message is 7 steps remain, but the demonstrated text component holds a fixed string. A complete sample integration plan says: arithmetic result = i32 7; desired content = that count in readable text; missing contract = conversion/binding mechanism; safe current draft = fixed orientation text, no dynamic-display claim.

Do not insert JavaScript template literals or call an invented toString method as if either were verified WillowScript. A concrete missing-contract note is progress: it names exactly what the future host or language design must provide before this integration can be implemented honestly.

Original learning-path task and reference

In a racing checkpoint editor, demonstrate build the beginner final project. 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.

Does an i32 result automatically become native text in the shown design?No; a conversion or binding contract must be suppliedYes; every integer renders itself in WUIXOnly when the helper is called remaining

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.

Connect prior calculation skills without inventing interpolation
A welcome project may want to show a calculated value, but a correct integer helper does not establish a text-conversion or interpolation API. Keep arithmetic evidence and UI integration contracts separate until the source supplies the bridge.
Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Name the exact missing bridge between your arithmetic helper and a dynamic welcome message.

Your recap

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