Separate cooperative tasks from native work — Review and demonstrate

PART I

Warm-up

Reconnect with a useful idea before starting separate cooperative tasks from native work. 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

Review scheduling evidence

A cooperative script task makes progress by the host’s scheduling rules; expensive native work may run behind a separate service boundary. Do not infer parallel execution, thread ownership or cancellation behavior from async/await alone. Specify the desired responsiveness and state ownership in a timeline before selecting any concrete host API.

Exercise design: a mod report screen starts native transformation jobJ for dataset revision 40. Script callbacks update the native UI only while screen owner O is active. The host must define scheduling, completion delivery and transform limits; the source supplies no complete worker/cancellation API. Timings below are illustrative ordering fixtures, not measured performance.

Supplied case: Learner predicts responsive UI but has no timing trace or host runtime.

Worked reasoning: The design establishes desired ordering and budgets only. A real responsiveness claim needs host version, workload, event latency and observation method. Keep native concurrency and script scheduling questions explicit.

Contrast and diagnosis: A short code sample and a public self-check cannot measure latency.

Worked reasoning and supplied artifact

// Disposable exercise fixture / host-contract notes; not executable API syntax.
// Supplied input: Learner predicts responsive UI but has no timing trace or host runtime.
// Worked prediction: The design establishes desired ordering and budgets only. A real responsiveness claim needs host version, workload, event latency and observation method. Keep native concurrency and script scheduling questions explicit.
// Rejected alternative: A short code sample and a public self-check cannot measure latency.

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: Cancelable workflow design. Build a small, understandable change around separate cooperative tasks from native work.

Create an evidence plan with 1000 and 100000 input rows, an interaction to observe, and the native/script metrics to record.

What to produce

Create an evidence plan with 1000 and 100000 input rows, an interaction to observe, and the native/script metrics to record. Include input → intermediate decision/state → predicted outcome, with any required host rule stated explicitly.

• 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;
import app;
domain Workspace {
    const application = Application({
        name: "Workspace",
        window: { title: "Dashboard", size: [1280, 800] },
        events: {
            "app.ready": fnc() -> void { console.log("Ready"); }
        }
    });
}

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.

• Review scheduling evidence
• Explain the decision for the supplied case, then independently work the changed fixture.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

In one or two sentences, name the decisive rule in “Review scheduling evidence” and predict the outcome of one changed input from your independent fixture. State which host behavior still needs real verification.

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