Plan DPI and text-layout tests — Flash-check repair

PART I

Warm-up

Reconnect with a useful idea before starting plan dpi and text-layout tests. 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

Repair a one-line assumption for translated text

DPI and text layout need explicit unit and measurement contracts. A logical layout size differs from physical pixels, and glyph measurements differ across fonts, scales and languages. Use small numeric budgets for predictions and native observations for actual rendering; no WUIX engine runs on this school site.

English label Open is measured40 logical units; German Öffnen is72. Content width60. Host contract wraps at approved word boundaries; these single-word labels may not be split, so an overlong word requires the documented overflow response.

Worked reasoning: Open fits. Öffnen exceeds by12 and cannot be assumed to wrap under this rule. The design must enlarge, truncate with an approved accessible full-label path, or report overflow according to a chosen host policy.

Failed alternative: Declaring both labels one line because they are translations ignores actual width; inventing character splitting contradicts the host rule.

Worked reasoning and supplied artifact

Open:40<=60 ->fit
Öffnen:72>60 ->overflow12
No approved internal word boundary
Needed:explicit resize/truncation/overflow contract

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: Accessible service console. Build a small, understandable change around plan dpi and text-layout tests.

Analyze labels Export width48 and Exportieren width84 in width70. Specify one explicit fallback and remaining native accessibility checks.

What to produce

A translation/measurement/overflow table and a chosen response 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.

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.

• Repair a one-line assumption for translated text
• Analyze labels Export width48 and Exportieren width84 in width70. Specify one explicit fallback and remaining native accessibility checks.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Use translated measurements rather than character-count guesses.

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