Choose an entry layout

InterfaceForge supplies the entry lifecycle and styling contract; Unreal supplies virtualized List View, Tile View and Tree View. A project can design the entry entirely in Blueprint without changing plugin source. Use stable model UObjects, On Entry Refreshed, On Entry Selection Changed and On Entry Released; call Notify Data Changed after model updates. See journal entries and field cards.

The shipped workflows use a List View for the journal's detailed rows and a Tile View for compact field summaries. The RTS provider exposes resource, selected group, objective, production and notice models; the RPG provider exposes party, objective, actions and status. Both are flat collections in these examples. A Tree View would add expansion and parent/child semantics without solving a player task in either interface. This release therefore does not advertise a completed hierarchical-tree workflow or provide a decorative tree showcase.

For a project that needs a hierarchy, use an engine Tree View and its On Get Item Children binding with project-owned parent/child models. Use an IFEntryWidget Blueprint as the entry class and the same assignment/update/release contract. Keep expansion state and child retrieval in your screen/data source; do not create a new entry subclass for every node type. Supply your own navigation/expansion affordances and validate recycled entries against the assigned model.

Apply Theme to List View accepts the engine's Tile View and Tree View subclasses. The current release evidence verifies live List/Tile workflows; Tree styling has preconstruction coverage only. Runtime Tree expansion, focus restoration and large hierarchical collections are not certified. This is a deliberate example-scope decision based on the actual player workflows, not a claim that a flat-list test validates trees.

Do not use a Scroll Box with thousands of manually created entry children when the engine's virtualized views fit the task. Preserve model identity when filtering/sorting; refresh changed models instead of recreating every entry. The journal's1,000/10,000-model tests and the field-card interaction tests document their own performance/input limits.