[color] Very generic colors: Rgb, Hsv and Gray

[TomSaw]

These Colors may be used on their own. F.e. passed to a colored LED driver or being emitted by color-sensor drivers.

They also represent single pixels for modm::graphic::Buffer and modm::graphic::Display (Work in progress, see feature/rewrite-graphic

Features

• Bit granularity for color::Gray. Same for color::Rgb and color::Hsv cause they're made from 3x color::Gray
  • Proportional conversion between grays with different digits. 2-bit Gray ---> 4-bit Gray f.e. converts as follows:
    • 0b00 --> 0b0000
    • 0b01 --> 0b0101 // No stupid lshift, the gap is filled up
    • 0b10 --> 0b1010
    • 0b11 --> 0b1111 // Saturated stays saturated, white stays white
• C++20 concepts for colortypes and colorgroups (currently ColorPlane and ColorPalletizing). These concepts support overall readability and enabled very nice overload resolution modulation for modm::graphic::Buffer and modm::graphic::Display (Coming soon, see feature/rewrite-graphic
• Any imaginable color conversion works - type, granularity, palletized or planar... doesn't matter.
• Operators with saturation arithmetics

TODO

• Requires [fix] modm::Saturated #780 being merged
• Implement some missing operators
• Optional range check for value in ProportionalUnsigned::ProportionalUnsigned(T value)
• Update header Timestamps

[TomSaw]

This is ready for a first review @salkinium
I also got my fingers on modm::Saturated again, improved the API and added another test SaturationTest::test__uint8_t_ref.

[salkinium]

So far I like it a lot, very nice design with the generic bit width!

[TomSaw]

Apologize my enduring "push --force" thunderstorm. I'm transitioning from poke mode to test local, push after success mode 😬

Tests passed @salkinium! What's left is a good solution for the ProportionalUnsigned constructor 🙄

[TomSaw]

These colors have been proven in the field. Adding code snippets to the docs (color.md) rounds up the package.

• We're left open with the issue of modm::ProportinoalUnsigned. Please have a look on my solution @chris-durand when you find a minute.

[chris-durand]

Please have a look on my solution @chris-durand when you find a minute.

I'll try to find some time tomorrow to look at the PR.

[TomSaw]

Wanna get some stuff off the table. This PR feels robust, if you find a minute @salkinium 😅...

[salkinium]

I'm fine with these changes, modulo my doc comment.
I'm two weeks from handing in my thesis, so cannot give you a technical review, but if @chris-durand approves this PR, I'll merge it.

[salkinium]

?

We generally don't promise future code in the documentation, cos we usually don't get it done in time ;-P

[chris-durand]

@TomSaw Did you see what I wrote in #781 (comment) ? The discussion got so lengthy that github hides most of it by default 😅

[TomSaw]

@TomSaw Did you see what I wrote in #781 (comment) ? The discussion got so lengthy that github hides most of it by default 😅

Nope. Totally missed that and check it tomorrow.

[salkinium]

I'm still very interested in merging this, unfortunately, I've completely lost the overview of the review. I think it's almost done, perhaps you want to address the least comments and then we can merge it?

[TomSaw]

Hey there. Yes it was almost done. Only chris requested to extract the "arbitrary integer" logic into its own class for good reasons, see #781 (comment) and #781 (comment)

Simple task but then, a strong force pulled me into another universe. One with a ton of PHP actually 🤕

I've just read the processing::fibers readme and it sounds gorgeous 🤩 congrats for completing this!

[TomSaw]

Nothing changed yet.. just cleaned up the tree