Pylerium local operations

Check out Pylerium!

Six additional GUI / Advanced / … applications combine real tool processes, recipe editing, terminal output, shared results, model previews and pipeline visualization. See Starter tools and projects. Standalone example files are in examples/advanced_workshop/.

Choose Workshop → New → GUI / … for a complete runnable application. Runnable starters also appear in Insert boilerplate and in focus mode. Start with GUI / Blank custom application for an independent window with your own layout. Add only the components you need; the toolkit supplies the shared style, not the operations application.

GUI starter	Reusable components
Blank custom application	Minimal window and your own layout, with shared panels and buttons
Panels and actions	Optional page navigation, panels and your own menu/toolbar actions
Forms and data pages	Settings inputs, selectors, checkboxes, tables and multipage navigation
Complete component gallery	Original icon buttons, loadout cards/sidebar, item selector dialog, stats, Python editor/focus card, ANSI console, lists, trees, tabs, sliders, progress, dialogs and file picker
Model preview and workflow	Original interactive model/material preview, statistics/controls and dependency map
Responsive background work	Worker-thread tasks with success/error callbacks delivered on the GUI thread

Insert boilerplate → GUI element / … provides nine small snippets: panels/buttons, forms, menus/toolbars, tabs/data views, dialogs/file pickers, editor/terminal, model canvas, workflow map and background tasks. Insert these into your window's __init__ after super().__init__(); insertion follows the current line's indentation. They add widgets to self.content; replace that layout with any layout in your own application. These snippets are insertion tools, not complete projects in the New dialog.

systematic_gui is the public toolkit; gui_components holds the same stylesheet and button, label, panel factories imported by the main application. Theme widgets come from the original menu classes. WorkflowMap, WorkshopEditor, EditorCard, TerminalConsole, model previews and item data use their original implementations. Menus, tabs, sliders and dialogs share the central style. All SDK modules are available through the runner's PYTHONPATH; create your own handlers and subclasses without duplicating styling.

from pylerium_gui import create_application, AppWindow, button, panel, run

class MyTool(AppWindow):
    def __init__(self):
        super().__init__('MY TOOL', 'LOCAL WORKSPACE')
        # Compose your own layout directly; pages are optional.
        card, box = panel()
        box.addWidget(button('Run', lambda: self.notice('Ready'), primary=True))
        self.content.addWidget(card)
        self.content.addStretch()

if __name__ == '__main__':
    app = create_application('My tool')
    window = MyTool()
    raise SystemExit(run(window))

GUI projects created from New are marked interactive and stay open until you close them or click Stop. They do not inherit the batch-job timeout. If you insert a GUI starter into an existing batch project, use an execution loadout with timeout 0. Keep file/network/CPU work in window.run_background(work, on_success, on_error); worker functions return data and callbacks update widgets. create_application reuses an existing QApplication, and run(window) holds the window through the event loop.

The packaged interpreter includes Qt, NumPy, Trimesh, Pillow and ModernGL for these starters and model previews. If selecting an external interpreter, install PyQt6 numpy trimesh pillow moderngl there. The runner passes the current workspace path so custom GUIs use the same assigned assets/background. AppWindow creates no operations store, plugin host or built-in workspace pages. Its content layout is yours. Navigation appears only when you call add_page; menus and toolbars appear only when you add them. Animated backgrounds are optional via motion=True. Pylerium Window remains an alias for older saved projects.