Article index

Read complete articles by topic.

• What is Nexus UI Web?
• Requirements and support
• Obtain the framework and prepare your environment
• Install and check runtime components
• Build your first add-on
• Integrate into an existing Blender add-on
• Choose how users open the interface
• Registration, binding, and cleanup
• Window position, size, and visibility
• Transparent shapes and drag regions
• Text, keyboard, and pointer input
• Value dragging and undo
• Connect your interface to Blender
• Call Python from the interface
• Keep the interface in sync with data
• Events and connection status
• Images, files, and mesh resources
• Drop, paste, and pick files
• Save files and export results
• Bring an existing Web UI into Blender
• Local resources and page restrictions
• Local preview and Blender verification
• Continue development and diagnose problems
• Framework updates and add-on coexistence
• Package and deliver your add-on
• Runtime architecture and responsibilities
• Resources, communication, and access boundaries
• Licensing and third-party attribution
• Framework entry points and lifecycle
• Window and page declarations
• Actions and call context
• State, queries, and refresh
• Events and notifications
• Resources and file configuration
• Errors, status, and panel hints
• Public types, enums, and results
• Runtime component command line
• Connection, actions, state, and events
• Resource readers and file tools
• Page markers and script loading
• Transform interactions
• Frontend adapters and existing helpers
• Page types and asynchronous results
• Clicking does not open a window
• The window opens but is completely invisible
• The page is blank or partly missing
• Runtime download or installation failed
• The button responds but nothing happens
• Blender data changed but the interface did not
• The header cannot be dragged
• Controls cannot be clicked or clicks pass through
• Images or file resources cannot be read
• Restart or version-conflict message