Implicit light/dark panels

Development
1

Reading another post regarding “dark panels” for a plugin where the developer may not be very active anymore gave me an idea.

The current Rack “prefer dark panels” scheme requires code changes in a module.

Imagine instead it followed conventions (look for a …“-light” / …“-dark” - named SVG in the res folder), then it would only be a matter of dropping a new appropriately-named SVG to enable the dark/light panels.

This isn’t without downsides. It wouldn’t work for all plugins, especially if any module does explicit drawing. It could also be seen as inviting problematic activities regarding ownership/copyright (I see that as more of a personal responsibility thing, personally).

… just a thought.

2 Likes
2

Could you elaborate on that? Wouldn’t doing that violate most standard open source licenses?

3

If you distribute the customizations, then yes, that would probably violate many licenses.

Currently, it’s trivial to replace a panel svg, and I’m not aware that there has been any significant exploitation of that fact. On physical rack, I don’t think it’s uncommon for people to modify, paint, label, or replace the front panels on their modules.

What I’m suggesting would enable the most minimal requirement for a developer to add alternate panels – no code changes whatsoever.

1 Like