There is no automatic layout engine in the NeL interface: every element pins itself to an anchor and optionally follows a size reference. It is a small model (nine hotspots, an offset, and a fractional size follow), and everything on screen is built from it.

Interface coordinates are in pixels with y pointing up: y="0" at an element's anchor, positive y moves toward the top of the screen, negative y moves down. Interface authors spend their lives writing y="-12" to move things down; this is normal.

Every element carries two sets of coordinates: the declared x/y/w/h (relative, as authored) and the computed x_real/y_real/w_real/h_real (absolute screen pixels, y-up from the bottom-left of the canvas). The real values are what scripts and hit tests read; they are exposed to Lua and <link> targets as reflected properties.

Each element has nine hotspots (corners, edge midpoints, and center):

TL  TM  TR
ML  MM  MR
BL  BM  BR

posref="PARENT SELF" pins the element's SELF hotspot onto the parent's PARENT hotspot. The default is BL BL. A single value sets both. x/y then offset from that pinned point.

Reading the pair aloud helps: posref="TR TL" = "my top-left on the parent's top-right", so the child hangs off the parent's right edge, tops aligned. This is how rows are chained (each element's posparent is the previous one):

<view type="text" id="a" posref="TL TL" x="12" y="-10" ... />
<view type="text" id="b" posparent="a" posref="BL TL" y="-4" ... />   <!-- below a -->
<view type="text" id="c" posparent="b" posref="MR ML" x="8" ... />    <!-- right of b, vertically centered -->

By default position is relative to the containing group. posparent="someid" anchors to any sibling instead (resolved as a short id within the same group, or a full ui:... id). posparent="parent" is the explicit default. Parent resolution is deferred to the end of parsing, so an element may name a sibling declared later in the file.

w/h set the size in pixels. Two behaviors to know:

• Default size is the parent's size, not zero, when the element sits inside a group. An element with no w at all follows its parent width silently.
• With sizeref, the axis follows a size reference element and w/h become additive deltas. sizeref is a string of w and/or h, each optionally followed by a digit meaning tenths:

The reference element defaults to the parent (or the posparent); sizeparent="id" selects another element. max_sizeref/max_sizeparent apply the same mechanics to an element's maximum size (useful with scrolling lists).

A classic full-width row inside a padded window:

<group id="log" posref="TL TL" x="12" y="-8" sizeref="w" w="-24" h="122"> ... </group>

Text views don't obey w. A type="text" view zeroes its w/h and sizes itself from its content. For multi-line text the wrap width is min(parent inner width, line_maxw); set line_maxw for a narrower column, a plain w attribute does nothing. multi_line_maxw_only="true" makes line_maxw absolute. {.is-warning}

Parsed by every view, control and group:

Groups additionally understand child_resize_w/child_resize_h (auto-size the group to enclose its children, plus child_resize_wmargin/hmargin), max_w/max_h clamps, and window-level attributes covered in Windows and containers.

<vector> clones a template instance N times with $i index substitution and automatic position chaining. This is how the showcase builds the Minesweeper board (81 cells), the console log and the inventory grid without 81 hand-written elements:

<vector template="doc_vec_cell" _size="8" _firstindex="0" _firstpos="TL TL"
        _xfirst="0" _yfirst="0" _nextpos="TR TL" id="c$i" i="$i" x="0" y="0" />

• _size sets the clone count; _firstindex (default 0) and _step (default 1) drive the $i values.
• $i is replaced in every attribute: ids, template params, positions.
• _firstpos is the first clone's posref; _nextpos the posref of every later clone, whose posparent is automatically set to the previous clone's id, so _nextpos="TR TL" builds a left-to-right row and "BL TL" a top-down stack. Both must be present for chaining; _xfirst/_yfirst override x/y on the first clone only.
• Grids are two (or more) vectors with different _firstindex and _yfirst, as in the inventory's two bag rows.

Remember the posref reading order: parent hotspot first. A left-to-right chain is TR TL ("my TL on the previous one's TR"), not TL TR.

Templates themselves (declaring one, parameter defaults, #param substitution) are covered in Interface XML structure.