I would like some thoughts from the maintainers as to how you want to handle such things, if at all. This could be a plugin model, with a hook in DeckConfig, a check like I am doing, or a few different things depending on how layout is also included in.

An option would be to have a list of "layout" classes that are matched, instead of the current DeckConfig architecture.

So lets try changing this to a "layout" class, such that plugins could even register their own layout. Some sort of a dictionary with "default" being the usual layout, and others can be added and such.

• Convert layout system to allow for class selection based on device (somehow) for non SD layouts
• Determine "Standard" layout components (dials, dials w/ touchscreens, keys, etc) and better abstract
• Determine how this interacts with lower-level control library
• Are new devices able to be plugins? Add "layout registration" feature