Arrange a column and spacing — Build the smallest useful slice

PART I

Warm-up

Reconnect with a useful idea before starting arrange a column and spacing. 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

Start with one child before adding spacing

Column layout combines ordered children with padding, gaps and available space. The source shows padding [24,32] and gap16 but does not settle every measurement convention. Each exercise supplies its own explicit geometry contract; do not generalize that contract into a universal WUIX guarantee.

A minimal status column contains one text child of height20. Host geometry uses top/bottom padding8 and no border. The chosen gap12 applies only between children.

Worked reasoning: One child has no adjacent partner, so gap contributes zero. Total height is8+20+8=36. Adding a second height20 child later introduces exactly one gap and total68.

Failed alternative: Counting gap for a single child invents trailing space and predicts48 for the minimal slice.

Worked reasoning and supplied artifact

One child: 8 + 20 + 8 = 36
Two children: 8 + 20 + 12 + 20 + 8 = 68
Gap contribution: 0 then12
Minimum configuration: column + one text + padding8

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 arrange a column and spacing.

Compare one and two height24 children with padding6 and gap8. Predict totals before writing the proposed configuration.

What to produce

A minimal column description and one-child/two-child geometry comparison.

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

• Start with one child before adding spacing
• Compare one and two height24 children with padding6 and gap8. Predict totals before writing the proposed configuration.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Count adjacent pairs, not child count.

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