Use colour-coding for user disambiguation

[a-andreyev]

Contributes to issue #513
I like this HSL-based appoarch so tried to help (implemented similar for r0kk3rz Sailfish OS version), but feel to reject/correct :)

Checked with different KDE color schemes:

[KitsuneRal]

Thanks for the start! And yes, HSL-based calculation is certainly the way to go. We have a few more tasks ahead though :)

• Calculate colour in the library (Provide a colour code for the user libQuotient#296)
• Colour users in the user list as well
• Provide a switch to use colour disambiguation instead of full-name disambiguation

[a-andreyev]

current results screenshot:

[KitsuneRal]

Now that we have the lib PR, it's time to rebase this PR on the newest master :)

[KitsuneRal]

This PR should be really trivial now that the library does all the heavy-lifting. Let's do it!

[a-andreyev]

rebased and testing, getting black color for now (checking what versrion I've compiled)

[a-andreyev]

working now, but I have a boilerplate code for final color calculation from hue: for UserListDock widget c++ part and TimelineItem qml part. Not sure yet where's better place to provide shared solution 🤔

[KitsuneRal]

At the moment, all CI pipelines are breaking because you seem to have forgotten to add the newest lib to your commit. In order to do that, you have to make sure the contents under lib/ subdirectory are at the right commit (basically - the newest commit in master) and then commit the subdirectory itself (and push the commit, of course).

[KitsuneRal]

working now, but I have a boilerplate code for final color calculation from hue: for UserListDock widget c++ part and TimelineItem qml part. Not sure yet where's better place to provide shared solution 🤔

Well, a fancy way of doing it would be to introduce a Quaternion-specific user class (QuaternionUser) instead of the generic QMatrixClient::User (Connection allows you to customise the class it uses to create user objects) and provide QuaternionUser::color() that also backs a Q_PROPERTY so that it could be referred to from QML. If that sounds a bit too much for you, just leave the boilerplate - we'll get back to it sometime later.

[a-andreyev]

If that sounds a bit too much for you, just leave the boilerplate - we'll get back to it sometime later.

Probably a bit too much but sounds interesting 🙂 Agree to leave it for now and save the task as an issue for example