PART I
Warm-up
Reconnect with a useful idea before starting keep rendering behind native services. 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
Follow the native rendering request boundary
Rendering belongs behind the native service boundary described by WUIX. Scripts supply descriptions and receive documented outcomes; they do not acquire DOM, graphics-driver or native-handle authority by importing a UI library. Availability, permission, owner lifetime and acknowledgement remain separate checks.
Host receives description screenA, targetmain and capability ui.main. The capability is granted. Acknowledgement arrives after native creation succeeds. Scripts receive no raw native pointer.
Worked reasoning: The script validates the description, submits a request and awaits a documented outcome. Success permits a visible-state claim for main. It does not authorize pointer access or a second protected target.
Failed alternative: Treating the acknowledgement as a raw handle grant invents authority absent from this contract.
Worked reasoning and supplied artifact
Script description ->authorized host request ->native create ->acknowledged success
Returned evidence:main accepted
Not returned:native pointer,driver access,other-target capabilityIllustrative 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
Script description ->authorized host request ->native create ->acknowledged successRead this statement in its surrounding contract. Identify which value or host operation it contributes; do not infer an undocumented API.
Returned evidence:main acceptedRead this key/value within its containing object. State which parent owns it and the narrow visible behavior it configures.
Not returned:native pointer,driver access,other-target capabilityRead this key/value within its containing object. State which parent owns it and the narrow visible behavior it configures.
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 keep rendering behind native services.
Map a details-target request with uidetails granted but uimain denied. List the exact permitted boundary and unsupported claims.
What to produce
A request/authorization/native-effect/evidence diagram.
- 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.
Need a hint?
The supplied service deliberately returns an outcome rather than raw implementation authority.
Treating the acknowledgement as a raw handle grant invents authority absent from this contract.
Original learning-path task and reference
In a classroom scheduling assistant, demonstrate keep rendering behind native services. 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.
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.
- Follow the native rendering request boundary
- Map a details-target request with uidetails granted but uimain denied. List the exact permitted boundary and unsupported claims.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Read returned authority from the contract rather than from the word native.
This marks your personal practice record only. It is not a certification or an official workspace assessment.