Multi-instance Silo configuration UI #15
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Overview
Create a configuration UI for managing multiple Silo instances. Users should be able to add, edit, remove, and nickname Silo connections, with each instance appearing as a separate origin in the origin selector.
Parent Issue
Epic: #8 Unified File Origin System
Goals
Detailed Design
Origins Management Dialog
Accessible from "Manage Origins..." in origin selector dropdown:
Add/Edit Silo Dialog
Dialog Implementation
Configuration Storage
Preferences Integration
Add "Origins" page to Preferences dialog:
Migration from Old Config
Migrate existing single-instance Silo config:
Implementation Tasks
OriginManagerDialogclassSiloConfigDialogclassOriginsPreferencePageFiles to Create/Modify
src/Gui/OriginManagerDialog.h(new)src/Gui/OriginManagerDialog.cpp(new)src/Gui/SiloConfigDialog.h(new)src/Gui/SiloConfigDialog.cpp(new)src/Gui/OriginsPreferencePage.h(new)src/Gui/OriginsPreferencePage.cpp(new)src/Gui/DlgPreferences.cpp(add page)Acceptance Criteria
Dependencies
Blocking
None
Complete. Closing with code references:
src/Gui/OriginManagerDialog.h/.cpp(251 lines) — List view with Add/Edit/Remove/Set Defaultsrc/Gui/OriginManager.cpp— Multi-origin registration, preference persistence, default origin selectionsrc/Gui/FileOriginPython.cpp— Python wrapper enables Silo addon to register multiple instancessrc/Mod/Create/InitGui.py:60-75— Silo first-start check and settings integrationNote: Silo instance configuration (API URL, token, SSL) is handled by the Silo Python addon, keeping the C++ layer origin-agnostic by design.