Connector and Protocol definitions load-from-JSON

[connorjak]

At the moment, Connectatron uses C++ enums and the magic_enum library for automated operations like stringizing all enum names.

This has the following limitations:

• Must follow C++ variable name character restrictions
  • Partially solved by underscore-encoding
• No way to add more connectors and protocols
• Difficult to add associative information like Category in a very flexible way
  • Currently implemented categories as ranges of the enumerations, so any connector or protocol cannot exist in multiple categories

Benefits that should be preserved:

• Connectors and protocols are only stored by string name
  • Changes to enum-order and metadata like category, etc do not disrupt the validity of the saved string
• Exactly one place to edit information about a single connector/protocol, no matter how many aliases that has
• Software only allows you to apply/change valid connectors/protocols

[connorjak]

Possible features for a JSON-based set of definitions of connectors and protocols:

• Split the definitions across multiple files
• Common string fields for things like
  • Connector "Male Connector Also Fits In"
  • See-Also linking
  • Common uses
  • Tags
    • Would replace Categories
    • Many tags possible on any connector / protocol
  • AKA / Aliases
  • Per-connector default protocols
  • Protocol-dependencies
    • Ability to assign a set of Protocols which are a subset of a Protocol for:
      • Backwards compatibility
      • Standards containing other standards
  • Expanded Protocol details for:
    • AC Power Delivery
    • DC Power Delivery
    • More generic possibilities?

We would likely set up a GUI-based editor for adding/changing connectors and protocols in order to avoid accidental errors in formatting and string-matching resulting in runtime unexpected behavior.