Allow user to color code tracks

Neat side-project / wishlist idea. I agree color is a useful organizational tool that your brain is good at dealing with.

Oh yes. Something on the lines of tags in Mac? It could be added as a column next to the track name list with a drop down menu to select a colour. This would be a good addition indeed.

This is a good start.

Advanced:
* extend this to bitmaps
* overlays

Hey. I would like to work on this bug, but I had a suggestion/modification :

Rather than adding a new column for the color tag, we could make changes in dlgtrackinfo.cpp such that, it sets the background color for Trackno or Trackname ( or the entire cell, but that could look ugly) based on the what ptrack->getgenre() returns ?

We could think out the default colors for genre, and also the default for when none is specified.

Let me know if this is acceptable, otherwise i will work on what was specified till now.

You heading for a color code for genres only, right?
This is only useful for users who have cleaned up the genre tags for their entire library, so thats might be a bit to short to be a
gneric solution.

I would prefer to color tag the tracks independent from any other metadata, but add a feature that calculates a color from any cloumn on demand. This way we may use genre colors for some users, other my prefer Key or BPM.

For me the tack number column is useless for DJing, so it is hidden on my setup.
Using the Track name background or the font color would work for me.

An additional "cover" column for adding genre covers, colored rectangles or any other picture giving useful information would be also a good solution. We have also discussed to generate a picture using genre bpm and Key, but that is too advanced for this.

Oh yes, that makes more sense.
To give user the power to select the color, would require a pallete for them to the select color from ?

Could you hint me on how to get started ?

What will you go for? An extra column or a changing the background?
You may start with adding functions that allow to change the color of a track title.
I have now idea how, but I am sure you find something in the WWW.

If you go for the coloum solution. You may have a look at the cover column code. I am sure you can reuse a lot of this code.

For the color editor, it would be nice to do a scribbled mock-up, (you may use just inkscape or any other drawing tool of your choice)

In on of your early version it is OK, to use a hard coded color mapping of genres as you have purposed above.
This way we can have a early prove of concept.

Hope that helps, please keep asking if required.

No changing background colors in track names or other tricks please.
Keep it simple and add an separate color column, that can be hidden eventually.

Leave it to the user what they use the color column for.
A strict categorization based on existing genre tags is not flexible enough. If the user decide to use it like that , fine. He can filter by genre, select all, and apply a color. Others might want to apply color labels based on track energy, or track notation.

Id suggest to allow to select from a simple color scheme, according to https://www.beatunes.com/en/open-key-notation.html

Firstly, Thanks for helping out here.

Oh alright, though it was not the option i was working on, I think your suggestion is valid, as adding an extra coloumn is always better.

This might take time, as i am travelling this week, but i'll try to make most of the time i get.

I was able to add the color column in the track properties section, but i am somehow finding it too hard to add it in the right place.
Can i be further hinted ?
Sorry to keep you guys waiting for this :|
Thanks a lot for the patience.

You may add a pull request against master of your current state, and add a comment that there is work in progress.
Maybe we can give some hints than.

See the attached patch which is inspired by the star rating library
column and other parts of the Mixxx code. The rest of the new code
modifications is public domain. Please feel free to test, fix bugs
and submit to the main Mixxxx code repository.

Thank you very much for the patch.

I have not yet looked into it.

Did you consider to publish it as GitHub pull request.
This simplifies the review process a lot.

Here are some more hints:
http://www.mixxx.org/wiki/doku.php/bugfix_workflow

In order to commit your patch, we need your permission.
Please sign:
https://docs.google.com/a/mixxx.org/spreadsheet/viewform?formkey=dEpYN2NkVEFnWWQzbkFfM0ZYYUZ5X2c6MQ

and comment here when done.

By the way, what happens with your patch here?
https://bugs.launchpad.net/mixxx/+bug/1645054

Simplified and removed the editor class. I won't sign the
contributors agreement, but everyone is free to do whatever
they want with the code including uploading it to github.

PR#1771 beenisss (Y)

I probably would sign the agreement if the code
would be GPL with no exceptions and changes would
require my approval, no time limit.

But this patch is is free for all. Hope someone
can get this feature into Mixxx with or without
this patch.

It doesn't sound like it will be possible to use that patch if you don't want to sign the agreement, even if you otherwise consent to it explicitly.

@John Doe -- by "everyone is free to do whatever they want with the code", do you mean you are offering it into the public domain?

The code I have posted in this bug report is in the public domain.

Great you start working on this! In conjunction with the star rating this will be very helpful.
To pick a color per mood, energy or custom 'code' a rainbow palette would work best IMO.

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/6852