mirror of
https://github.com/ChuckBuilds/LEDMatrix.git
synced 2026-10-04 14:25:08 +00:00
* chore(scripts): delete unreferenced helper scripts None of these is referenced by an installer, systemd unit, CI workflow, test, the web UI or src/: - utils/cleanup_venv.sh removes venv_web_v2, which nothing creates - utils/clear_python_cache.sh hardcodes ~/LEDMatrix and a .webassets-cache nothing uses - install/migrate_config.sh only copies the template, which the installer and ConfigManager already do - install/debug_install.sh, debug/debug_web_manual.py - diagnose_web_ui.sh and verify_web_ui.sh overlap diagnose_web_interface.sh, which the docs point to - fix_internet_connectivity.sh is iptables-only (stale on nftables) - diagnose_plugin_permissions.sh, dev/validate_python.py - download_nba_logos.py + README_NBA_LOGOS.md: logo_downloader fetches logos on demand - setup_plugin_repos.py linked into the production plugin-repos/ dir; the dev workflow is scripts/dev/dev_plugin_setup.sh, and MULTI_ROOT_WORKSPACE_SETUP.md now uses it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(config): drop unused plugin_system flags and a dead unit comment - config.template.json: remove plugin_system.auto_discover, auto_load_enabled and development_mode. Nothing reads them; the web UI only stores them when a client sends them. ConfigManager's migration only adds template keys, so existing configs keep theirs unchanged. - config.template.json: re-indent vegas_scroll's live_* keys. - systemd/ledmatrix.service: remove the comment documenting LEDMATRIX_ON_DEMAND_PLUGIN / on_demand_env.conf; nothing reads either. - CONFIG_REFERENCE.md: say the legacy keys are no longer in the template. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: delete docs/archive and PLUGIN_IMPLEMENTATION_SUMMARY.md - docs/archive/: superseded guides; the repository history keeps them and no live doc links into the directory. The one open document in it, WEB_UI_AUDIT_2026-09.md, moves to docs/audits/ and is linked from the docs index. - PLUGIN_IMPLEMENTATION_SUMMARY.md invented usage statistics, called v2.0.0 current, listed shipped auto-updates as future work and documented a BasePlugin.get_config() that does not exist. - docs/README.md: drop both, and stop telling contributors to archive obsolete pages instead of deleting them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(plugin-api): fix extra_small_font size, cache metric key and scroll pacing example - PLUGIN_API_REFERENCE: extra_small_font loads at 7, not 6 (crisp_size snaps it, src/display_manager.py); get_cache_metrics() returns cache_hit_rate, not hit_rate (src/cache/cache_metrics.py). - ADVANCED_PLUGIN_DEVELOPMENT: the basic scrolling example slept in a loop and never passed frame_hold; use ScrollHelper + scroll_config.configure() and set_scrolling_state(True, frame_hold=...) as PLUGIN_API_REFERENCE does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(plugin-config): match the config tab, icon and web-action docs to the code - PLUGIN_CONFIG_QUICK_START / PLUGIN_CONFIGURATION_TABS / PLUGIN_CONFIGURATION_GUIDE: there is no "Reset to Defaults" button (the tab has Refresh, Update, Uninstall, Save Configuration); plugin config hot-reloads (ConfigService + on_config_change), so no restart; the schema is found by the fixed name config_schema.json, not a manifest config_schema field; the tab row is "Plugin Manager", not "Plugins"; forms are server-rendered from /v3/partials/plugin-config/<id>; the duration hook is get_display_duration()/display_duration; a class_name mismatch raises PluginError; the store requires id, name, class_name and display_modes (not version); plugin_system.debug/log_level do not exist (use run.py -d / LEDMATRIX_DEBUG). Drop "future" features that shipped. - PLUGIN_CONFIG_CORE_PROPERTIES: list all of CORE_PLUGIN_PROPERTIES, including skin, skin_options and the vegas_* tuning keys. - PLUGIN_CUSTOM_ICONS: icon is only a Font Awesome class (fallback fa-puzzle-piece); emoji/URL icons and getPluginIcon() never existed in v3. Note that /api/v3/plugins/installed currently omits icon. - PLUGIN_WEB_UI_ACTIONS (+ example JSON): success_message, error_message and step1_message are never read. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(store): describe the monorepo registry and the store UI as they are - PLUGIN_STORE_GUIDE: the Plugin Store is a section of the Plugin Manager tab; URL installs are "Install from GitHub" -> "Install Single Plugin"; bulk update exists (Check & Update All) plus opt-in weekly auto-update; PluginStoreManager() defaults to plugins/, so the Python examples pass plugin-repos; registry plugins are downloaded (GitHub API, ZIP fallback), not cloned; updates compare version with latest_version. - PLUGIN_REGISTRY_SETUP_GUIDE: replace the per-plugin-repo + tag walkthrough with a short page on the monorepo registry (plugin_path, latest_version, update_registry.py) that points at the monorepo's own SUBMISSION.md. Drops the reference to the deleted PLUGIN_IMPLEMENTATION_SUMMARY.md and setup_plugin_repos.py. - plugin_registry_template.json: use the real entry shape. - PLUGIN_QUICK_REFERENCE: automatic background updates exist (opt-in); registry example and publishing steps use the monorepo, not tags. - PLUGIN_DEVELOPMENT_GUIDE: tags/releases are not read by the store. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(readme): fix the Triple Bonnet mapping, install prerequisites and backup names - README: the Adafruit Triple Bonnet uses `regular` (3 outputs), not `regular-pi1` (1 output) -- src/matrix_support.py MAPPING_OUTPUTS, and the README's own hardware_mapping section; the template default mapping is adafruit-hat, the PWM mod switches it to adafruit-hat-pwm; manual install only needs git up front (first_time_install.sh installs python-dev-is-python3, cmake, ninja-build etc.; cython3/scons are not used); the Pi Zero 2 W is a supported low-memory board, consistent with PRODUCT.md, LOW_MEMORY_BOARDS.md and the installer's low-memory build; fix the "First_time_install.sh" spelling, an orphan "2." list item and the hello-world starter link (it lives in the plugins monorepo). - CONFIG_DEBUGGING: automatic backups are config/backups/config.json.backup.<YYYYMMDD_HHMMSS_ffffff> (five kept), not config_YYYYMMDD_HHMMSS.json. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(dev): correct the test-running and rgbmatrix build instructions - HOW_TO_RUN_TESTS: coverage is not collected by a plain pytest run and pytest.ini has no threshold; the only one is --cov-fail-under=52 in the core unit-test job of .github/workflows/test.yml, which runs the whole test/ tree (not an allowlist). Almost no tests carry markers, so -m integration / -m slow select nothing; drop them and -m unit as the quick check. Replace the hardcoded /home/chuck path. - DEVELOPMENT: the rgbmatrix package is built with pip install . from the submodule root (scikit-build-core + CMake + Ninja), as first_time_install.sh does; there is no make build-python / bindings/python step, and the build deps are python-dev-is-python3, cmake and ninja-build, not cython3/scons. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(wifi): the setup AP is open; auto-enable can be turned off without code changes - WIFI_NETWORK_SETUP / SSH_UNAVAILABLE_AFTER_INSTALL: both AP paths in src/wifi_manager.py create an open network and nothing reads ap_password, so drop the "ledmatrix123" password and the ap_password key/advice. - SSH_UNAVAILABLE_AFTER_INSTALL: disabling automatic AP mode does not need code changes -- auto_enable_ap_mode is a WiFi-tab toggle and POST /api/v3/wifi/ap/auto-enable; note the monitor daemon reads wifi_config.json at start, so restart it after changing the setting. Use the ledpi username and a relative install path like the other docs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(reference): add auto_update, drop drifted line numbers, fix UI and service details - CONFIG_REFERENCE: document the top-level auto_update.enabled key (read by web_interface/auto_update.py and src/auto_update_setup.py); replace drifted file:line references with function names; the template's dim_schedule mode is "global". - ADVANCED_FEATURES: core does not read a per-plugin background_service block (the sports plugins read their own), and priority is "higher number = higher priority" on FetchRequest but not used for ordering. - WEB_INTERFACE_GUIDE: the General tab toggle is "Web Display Autostart" (web interface service), brightness is 1-100, and config paths are relative to the LEDMatrix folder, not /config. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: drop references to code removed in #608 get_installed_plugin_info, WiFiManager's saved_networks and the six always-skipping plugin test files are deleted there. NetworkManager already remembers joined networks; LEDMatrix no longer stores WiFi passwords. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: don't link SKIN_SYSTEM.md from the core-properties page #615 deletes SKIN_SYSTEM.md; with this link, whichever of the two merged second would break test_doc_links. The skin/skin_options entries go when #615 removes the keys. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
216 lines
5.3 KiB
Markdown
216 lines
5.3 KiB
Markdown
# Plugin Configuration Tabs - Quick Start Guide
|
|
|
|
## 🚀 Quick Start (1 Minute)
|
|
|
|
### For Users
|
|
|
|
1. Open the web interface: `http://your-pi-ip:5000`
|
|
2. Open the **Plugin Manager** tab
|
|
3. Find a plugin in the **Plugin Store** section (e.g., "Hello World")
|
|
and click **Install**
|
|
4. Notice a new tab appears in the second nav row with the plugin's name
|
|
5. Click that tab to configure the plugin
|
|
6. Modify settings and click **Save Configuration**. The running display
|
|
picks the change up by itself; no restart is needed
|
|
|
|
That's it! Each installed plugin automatically gets its own configuration tab.
|
|
|
|
## 🎯 What You Get
|
|
|
|
### Before This Feature
|
|
- All plugin settings mixed together in the Plugins tab
|
|
- Generic key-value inputs for configuration
|
|
- Hard to know what each setting does
|
|
- No validation or type safety
|
|
|
|
### After This Feature
|
|
- ✅ Each plugin has its own dedicated tab
|
|
- ✅ Configuration forms auto-generated from schema
|
|
- ✅ Proper input types (toggles, numbers, dropdowns)
|
|
- ✅ Help text explaining each setting
|
|
- ✅ Input validation (min/max, length, etc.)
|
|
|
|
## 📋 Example Walkthrough
|
|
|
|
Let's configure the "Hello World" plugin:
|
|
|
|
### Step 1: Navigate to Configuration Tab
|
|
|
|
After installing the plugin, you'll see a new tab:
|
|
|
|
```
|
|
[Plugin Manager] [Hello World] ← New tab! (second nav row)
|
|
```
|
|
|
|
### Step 2: Configure Settings
|
|
|
|
The tab shows a form like this:
|
|
|
|
```
|
|
Hello World Configuration
|
|
A simple test plugin that displays a customizable message
|
|
|
|
✓ Enable or disable this plugin
|
|
[Toggle Switch: ON]
|
|
|
|
Message
|
|
The greeting message to display
|
|
[Hello, World! ]
|
|
|
|
Show Time
|
|
Show the current time below the message
|
|
[Toggle Switch: ON]
|
|
|
|
Color
|
|
RGB color for the message text [R, G, B]
|
|
[255, 255, 255 ]
|
|
|
|
Display Duration
|
|
How long to display in seconds
|
|
[10 ]
|
|
|
|
[Refresh] [Update] [Uninstall] [Save Configuration]
|
|
```
|
|
|
|
### Step 3: Save and Apply
|
|
|
|
1. Modify any settings
|
|
2. Click **Save Configuration**
|
|
3. See the confirmation notification. Plugin settings apply live: the
|
|
display service reloads `config.json` when it changes and passes the new
|
|
settings to the plugin's `on_config_change()`
|
|
|
|
## 🛠️ For Plugin Developers
|
|
|
|
### Minimal Setup
|
|
|
|
Create `config_schema.json` in your plugin directory:
|
|
|
|
```json
|
|
{
|
|
"$schema": "http://json-schema.org/draft-07/schema#",
|
|
"type": "object",
|
|
"properties": {
|
|
"enabled": {
|
|
"type": "boolean",
|
|
"default": true,
|
|
"description": "Enable this plugin"
|
|
},
|
|
"message": {
|
|
"type": "string",
|
|
"default": "Hello!",
|
|
"description": "Message to display"
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
**Done!** The file name is fixed: the web interface looks for
|
|
`config_schema.json` in the plugin's directory; there is no manifest field
|
|
for it. Every installed plugin gets a tab; the schema is what turns it into a
|
|
form.
|
|
|
|
**Bonus:** an `icon` field in `manifest.json` names a Font Awesome class for
|
|
the tab (`"icon": "fas fa-star"`). See
|
|
[PLUGIN_CUSTOM_ICONS.md](PLUGIN_CUSTOM_ICONS.md).
|
|
|
|
## 🎨 Supported Input Types
|
|
|
|
### Boolean → Toggle Switch
|
|
```json
|
|
{
|
|
"type": "boolean",
|
|
"default": true
|
|
}
|
|
```
|
|
|
|
### Number → Number Input
|
|
```json
|
|
{
|
|
"type": "integer",
|
|
"default": 60,
|
|
"minimum": 1,
|
|
"maximum": 300
|
|
}
|
|
```
|
|
|
|
### String → Text Input
|
|
```json
|
|
{
|
|
"type": "string",
|
|
"default": "Hello",
|
|
"maxLength": 50
|
|
}
|
|
```
|
|
|
|
### Array → Comma-Separated Input
|
|
```json
|
|
{
|
|
"type": "array",
|
|
"items": {"type": "integer"},
|
|
"default": [255, 0, 0]
|
|
}
|
|
```
|
|
User enters: `255, 0, 0`
|
|
|
|
### Enum → Dropdown
|
|
```json
|
|
{
|
|
"type": "string",
|
|
"enum": ["small", "medium", "large"],
|
|
"default": "medium"
|
|
}
|
|
```
|
|
|
|
## 💡 Pro Tips
|
|
|
|
### For Users
|
|
|
|
1. **Navigate Back**: Switch to the **Plugin Manager** tab to see the
|
|
full list of installed plugins
|
|
2. **Check Help Text**: Each field has a description explaining what it does
|
|
3. **No Restart Needed**: Saved plugin settings apply to the running display
|
|
|
|
### For Developers
|
|
|
|
1. **Add Descriptions**: Users see these as help text - be descriptive!
|
|
2. **Use Constraints**: Set min/max to guide users to valid values
|
|
3. **Sensible Defaults**: Make sure defaults work without configuration
|
|
4. **Test Your Schema**: Use a JSON Schema validator before deploying
|
|
5. **Order Matters**: Properties appear in the order you define them
|
|
|
|
## 🔧 Troubleshooting
|
|
|
|
### Tab Not Showing
|
|
- Check that the plugin is installed and listed under **Plugin Manager**
|
|
- Refresh the page
|
|
- Check browser console for errors
|
|
|
|
### Settings Not Saving
|
|
- Ensure plugin is properly installed
|
|
- Check that all required fields are filled
|
|
- Look for validation errors in browser console
|
|
|
|
### Form Looks Wrong
|
|
- Check that `config_schema.json` is in the plugin's directory
|
|
- Validate your JSON Schema
|
|
- Check that types match your defaults
|
|
- Ensure descriptions are strings
|
|
- Look for JavaScript errors
|
|
|
|
## 📚 Next Steps
|
|
|
|
- Read the full documentation: [PLUGIN_CONFIGURATION_TABS.md](PLUGIN_CONFIGURATION_TABS.md)
|
|
- Check the configuration architecture: [PLUGIN_CONFIG_ARCHITECTURE.md](PLUGIN_CONFIG_ARCHITECTURE.md)
|
|
- Browse example plugins in the
|
|
[ledmatrix-plugins](https://github.com/ChuckBuilds/ledmatrix-plugins)
|
|
repo, especially `plugins/hello-world/` and `plugins/clock-simple/`
|
|
- Join the community for help and suggestions
|
|
|
|
## 🎉 That's It!
|
|
|
|
You now have dynamic, type-safe configuration tabs for each plugin. No more manual JSON editing or cluttered interfaces - just clean, organized plugin configuration.
|
|
|
|
Enjoy! 🚀
|
|
|