Capability types

[fxedel]

Closes #267. #177 and #437 will be added in a future pull request, but we make the syntax ready to make it easy later.

Some links:

• Capability schema improvements #267 for the initial idea, plus the capability type concept
• QLC+ forum: "How to help?"
• QLC+ document: "Fixture definition rework"
• QLC+ issue: "Fixture definition rework"

Todo

• Schema
  • Add capability types with type-specific properties
  • Remove channel type
  • Divide schema into several files for better readability
  • Allow BPM as unit (see add fixture 'minuit-une/m-carre' #460)
  • Allow "infinite" as value for pan/tiltMax
  • Add Hue, Saturation capability types (work for Better handle HSV/HSB/HSI/HSL channels #505)
  • Rethink capability type order (also update documentation and UI)
  • Rethink type-specific property order (also update documentation and UI)
  • Add soundControlled to ShutterStrobe?
• Model
  • Parse new capabilities (except ColorPreset)
  • Color names <-> Hex codes (work for Alternatives for color hex strings #437)
  • Handle start/end colors
  • Auto-generate:
    • channel.type
    • channel.color
    • channel.invert
    • channel.crossfade
    • capability.name
    • capability.menuClick? Do this in another PR
    • capability.helpWanted for ColorPreset capabilities without a colors property Do this in another PR
• Fixture test
  • Remove a lot of no-longer-used code
  • Migrate category tests (which mainly depend on channel types)
  • Validate start/end values: Should be of the same unit and either both or none of them with keyword
  • Add new type-specific checks
    • Pan/Tilt (Continuous): Check if angle doesn't conflict with physical's angle (maybe warn if not whole possible angle is used?)
    • ShutterStrobe: speed only allowed when shutterEffect is neither Closed nor Open
    • Effect: error when effectName would also be a valid effectPreset
  • Channels with only a Nothing capability should not define fine channels or similar stuff
  • If index has different start / end values: colors must not be stepped!
• Adapt usage to new capabilities
  • Fixtures (see Migrate fixtures to new capability syntax #478)
    • Test fixtures
  • Plugins
    • e:cue export
    • e:cue import
    • D::Light export
    • Millumin export (downgrading needed!)
    • QLC+ export
    • QLC+ import
  • UI (not much to do because model generates capability names)
  • Editor
    • Add more type-specific hints
  • everywhere else
• Update documentation
  • Add a note about the single capability shorthand
  • Rethink capability type order (see schema)
• Things to do shortly before merging
  • Test all code examples in the documentation
  • Re-add colors property for ColorWheelIndex capabilities
  • Check all helpWanted properties in the fixtures
  • Remove migration helper script (won't be needed anymore)
  • Update lastModifyDate in all fixtures
  • Draft a release

[fxedel]

@FloEdelmann Please already review the schema, the capability type documentation and the 12 fixtures that have already been adapted to the new syntax. Hopefully, we can finalize the syntax then so we can update the remaining 99 fixtures without worrying about bigger schema changes in the further lifetime of this PR.