FNS_CommandKit

Command Kit #

Your component's commands appear in the TDXL launcher palette (> / ?) without it having to know anything about the registry. Drop this COMP inside your component, mark the methods you want exposed, and they show up.

It is guarded throughout: when the launcher's companion is not in the session, nothing happens and nothing errors. A component carrying the kit works exactly the same for someone who never installs the launcher.

Adopting it #

1. Drag the COMP in as a direct child of your component's root.
2. Mark your commands (either way below).
3. Done — the kit announces your component on load, once you actually declare something. After changing your command set at runtime: op('FNS_CommandKit').Announce().

Decorator — derives everything from your code #

FNSCommand = op('FNS_CommandKit').mod('FNSCommand')  # import

class MyToolExt:
    @FNSCommand.fns_command(help='Set the project tempo')
    def SetBpm(self, bpm: float = 120, sync: bool = False):
        ...

The label comes from the CamelCase name, the help from the docstring's first line, and the prompted parameters from the signature — type hints become styles, typing.Literal[...] becomes a menu, and a parameter with no default is required. Extras: fns_command(label=…, help=…, hidden=True, params=[…]).

Explicit spec — no imports at all #

Promote a FnsCommand spec instead, for components that would rather not import anything. See the kit's own README DAT for that form.

Rules worth knowing #

• Command ids are permanent. Launcher curation, history and user presets key on tool#id, and the id derives from the method name — so renaming a shipped method orphans all three. Treat every shipped id as public API.
• Handlers run synchronously on the main thread. Return quickly and kick long work off with run(..., delayFrames=1).
• Caps: 24 commands per component, 6 parameters per command.

Components inside the FNS toolkit do not need this kit — they already carry an ExtUtils with the announcer in it. This is for everything else.