FNS_HubRegistry

Hub Registry #

The raw registry that decides what FNS_Hub shows: one entry per tab, with its label, order, visibility and what it renders. The hub itself holds no tab knowledge -- it draws what this registry says, and the registry injects one mirror or viewer per entry into the hub's tab area, prunes the ones whose tool is gone, and heals the rest.

It ships as its own core package, promoted to /sys (global shortcut op.FNS_HUBREGISTRY), alongside the six surface registries, FNS_Console and FNS_Updater. You normally never touch it directly; the hub is the UI.

For tool authors #

A tool that wants a hub tab ships a small host copy of this registry and registers itself on load -- the same shape as a toolbar or navbar entry. The host's Registration page names the tab:

• Tool COMP -- the contributing tool (defaults to the host's parent).
• Tab Content -- what to show: empty for the tool itself (it must be a panel), a panel COMP inside the tool (mirrored, so it can live anywhere), or a DAT/CHOP/TOP/SOP/POP (an OP Viewer).
• Tab Parameters -- a page scope instead: a Parameter COMP view of the tool (* for every page).
• Show in Hub / Shown in Hub / Tab Label / Tab Order / Help URL -- the usual publishing controls; Shown in Hub is what the hub's close button writes back to, so a hidden tab stays hidden across projects.

From Python, op.FNS_HUBREGISTRY.RegisterTab(comp, 'mytool', content=panel, label='My Tool', order=50) does the same; Tabs(), SetTabDisplayed(), Open(tab=) and OpenDocs() are the rest of the API. A component that must know when its tab is shown (a Web Render, say) implements OnHubExposure(exposed) on its extension; a palette Web Browser has its Active switched for it.