jwetzell / showbridge Goto Github PK

• control
• timecode
• etc

Simple as that.

The launcher is pretty clueless about the "status" of the underlying showbridge process.

It would be nice if it knew that the router was up and accepting traffic and do stuff like disable the web UI button until it is actually up.

Also might be nice for general running status and ability to restart the underlying showbridge process without restarting the launcher.

The error paths seem to get "confused" when a trigger or item is deleted. This leads to wrong items being highlighted.

• instructions for using the desktop launcher
• examples w/video/gifs
• sample configs
• protocol pages
• pages for each trigger/action/transform
• page for each message type
• formatting of existing things
• pages for how to interact with webui

• should be able to receive input from serial devices
• should be able to write to serial devices
• would be nice to use the devices section to save them and reference them easily

The other panels have a right-click action menu but the main protocol layout still has Add/Paste buttons so is inconsistent with the rest of the web ui.

The launcher currently creates a backup of config files whenever a change is applied to the router. It would be nice if these could be loaded from the UI either via the tray icon or via a separate window.

npm run dev in the cli folder no longer live reloads lib changes

The showbridge router has a general key/value store and it would be nice to be able to populate it on load. Also ability to update externally would be nice.

• lib: ability to set router vars programmatically
• lib: ability to set router vars via http
• main: ability to set router vars via process messages
• main: ability to load in vars on startup (from file)

Examples

• template: template is malformed or errors
• map: map key does not exist, value in map does not exist
• for all number based transforms what if the referenced property is not a number

Only reload the parts of the router that are necessary. This should primarily address protocol reloading.

• this is possible with the exec command and should be pretty easy
• how the environment param should look IMO would either be a string KEY1=VALUE1,KEY2=VALUE2 or an object (which it will need to be converted into anyways for passing to exec)

Not sure how long I can keep just a blue square as an icon.

When there is an error in the config there is no indication of where the error is? It would be nice if the Trigger, Action, .etc with an error would stick out in some way.

• what should happen if a connection (TCP, MQTT, etc.) goes down
• attempt reconnect? retry limit? backoff?
• user configurable?

would be nice to start a sort of "snippets" library and have that presented to the user in the webui

Often times a network destination or midi device will be referenced over and over again throughout a config. It would nice if there was a way to point an action params to a patch for easy reference and easy updating of info (IP/Port change).

Right now showbridge can send TCP to any endpoint that is reachable over the network, but currently just eats any responses it gets over those sockets. It would be nice if those responses could be handled.

This is going to be a bit hard but there are a lot of places with arrays that can be input, especially arrays of objects. Having a clean interface for those fields would be nice.