[GH-ISSUE #5493] [FR] More colours or colour picker for select #2445

Closed
opened 2026-03-23 21:22:25 +00:00 by mirror · 16 comments
Owner

Originally created by @OctoShotG on GitHub (Jun 8, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/5493

Description

image
More colour options or a colour picker, such as brown, white, black, red, etc

Impact

Easier to make statuses more distinct through colours visible in grid view

Additional Context

No response

Originally created by @OctoShotG on GitHub (Jun 8, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/5493 ### Description ![image](https://github.com/AppFlowy-IO/AppFlowy/assets/99288687/a3f79bb6-a07f-498f-8ac8-84e15b260fe5) More colour options or a colour picker, such as brown, white, black, red, etc ### Impact Easier to make statuses more distinct through colours visible in grid view ### Additional Context _No response_
Author
Owner

@MayurSMahajan commented on GitHub (Jun 17, 2024):

Should more colours be added here, or a way to add a custom colour should be added ?

<!-- gh-comment-id:2172578251 --> @MayurSMahajan commented on GitHub (Jun 17, 2024): Should more colours be added here, or a way to add a custom colour should be added ?
Author
Owner

@OctoShotG commented on GitHub (Jun 17, 2024):

Being able to pick any custom colour with something such as a RGB value would be be great for customising- most of the colours now feel quite dark and don't fit the best with some themes.

<!-- gh-comment-id:2172585746 --> @OctoShotG commented on GitHub (Jun 17, 2024): Being able to pick any custom colour with something such as a RGB value would be be great for customising- most of the colours now feel quite dark and don't fit the best with some themes.
Author
Owner

@nebiyuelias1 commented on GitHub (Jun 21, 2024):

So is the custom color input the way to go? I will be happy to work on this issue @apomalyn.

<!-- gh-comment-id:2182364170 --> @nebiyuelias1 commented on GitHub (Jun 21, 2024): So is the custom color input the way to go? I will be happy to work on this issue @apomalyn.
Author
Owner

@MayurSMahajan commented on GitHub (Jun 26, 2024):

Hey @nebiyuelias1, assigning this to you. Just make sure that the custom colour input is consistent with custom colour inputs we have used in other places within appflowy. Have fun contributing!

<!-- gh-comment-id:2190717501 --> @MayurSMahajan commented on GitHub (Jun 26, 2024): Hey @nebiyuelias1, assigning this to you. Just make sure that the custom colour input is consistent with custom colour inputs we have used in other places within appflowy. Have fun contributing!
Author
Owner

@nebiyuelias1 commented on GitHub (Jun 26, 2024):

Hey @nebiyuelias1, assigning this to you. Just make sure that the custom colour input is consistent with custom colour inputs we have used in other places within appflowy. Have fun contributing!

Oh exciting! So I saw some color picker with a dialog in the settings page. Do you think I should use that one?

<!-- gh-comment-id:2190721451 --> @nebiyuelias1 commented on GitHub (Jun 26, 2024): > Hey @nebiyuelias1, assigning this to you. Just make sure that the custom colour input is consistent with custom colour inputs we have used in other places within appflowy. Have fun contributing! Oh exciting! So I saw some color picker with a dialog in the settings page. Do you think I should use that one?
Author
Owner

@MayurSMahajan commented on GitHub (Jun 28, 2024):

Something more like this. This appears when you try changing highlight or text colour

Screenshot 2024-06-28 at 11 13 02 AM
<!-- gh-comment-id:2196184189 --> @MayurSMahajan commented on GitHub (Jun 28, 2024): Something more like this. This appears when you try changing highlight or text colour <img width="754" alt="Screenshot 2024-06-28 at 11 13 02 AM" src="https://github.com/AppFlowy-IO/AppFlowy/assets/47064215/a2d610f8-61bc-4623-b5c1-0d42a64398d2">
Author
Owner

@nebiyuelias1 commented on GitHub (Jul 4, 2024):

@MayurSMahajan I was able to add the custom color picker to the UI, but I was wondering how I could modify the protocol buffer to allow custom input. Right now it seems it's set to use integer values with an enum. Do you have any suggestions?

<!-- gh-comment-id:2208992542 --> @nebiyuelias1 commented on GitHub (Jul 4, 2024): @MayurSMahajan I was able to add the custom color picker to the UI, but I was wondering how I could modify the protocol buffer to allow custom input. Right now it seems it's set to use integer values with an enum. Do you have any suggestions?
Author
Owner

@MayurSMahajan commented on GitHub (Jul 5, 2024):

@nebiyuelias1 Actually I am not the best person for this question, I haven't really worked on the colour pickers. I would advice you look up the existing implementation in here:
https://github.com/AppFlowy-IO/appflowy-editor/blob/main/lib/src/editor/toolbar/desktop/items/color/color_picker.dart

See if that helps, otherwise we'll ask someone who knows this for help.

<!-- gh-comment-id:2210197275 --> @MayurSMahajan commented on GitHub (Jul 5, 2024): @nebiyuelias1 Actually I am not the best person for this question, I haven't really worked on the colour pickers. I would advice you look up the existing implementation in here: https://github.com/AppFlowy-IO/appflowy-editor/blob/main/lib/src/editor/toolbar/desktop/items/color/color_picker.dart See if that helps, otherwise we'll ask someone who knows this for help.
Author
Owner

@nebiyuelias1 commented on GitHub (Jul 5, 2024):

@MayurSMahajan Thanks for the reply. I did check that widget but it looks like the way it works is different. Because for the value I'm trying to implement it's using a proto buff with a set of options. What I'm struggling with is how to map a custom hex value with a string to a way that is going to be used by the proto buff. A nudge in the right direction would be helpful.

<!-- gh-comment-id:2210320063 --> @nebiyuelias1 commented on GitHub (Jul 5, 2024): @MayurSMahajan Thanks for the reply. I did check that widget but it looks like the way it works is different. Because for the value I'm trying to implement it's using a proto buff with a set of options. What I'm struggling with is how to map a custom hex value with a string to a way that is going to be used by the proto buff. A nudge in the right direction would be helpful.
Author
Owner

@MayurSMahajan commented on GitHub (Jul 9, 2024):

Again I am not really familiar with this part of codebase, nor with protobuffs. Sorry about that!

<!-- gh-comment-id:2216523072 --> @MayurSMahajan commented on GitHub (Jul 9, 2024): Again I am not really familiar with this part of codebase, nor with protobuffs. Sorry about that!
Author
Owner

@nebiyuelias1 commented on GitHub (Jul 9, 2024):

Again I am not really familiar with this part of codebase, nor with protobuffs. Sorry about that!

Ok who should I ask?

<!-- gh-comment-id:2216719357 --> @nebiyuelias1 commented on GitHub (Jul 9, 2024): > Again I am not really familiar with this part of codebase, nor with protobuffs. Sorry about that! Ok who should I ask?
Author
Owner

@MayurSMahajan commented on GitHub (Jul 9, 2024):

Discord would be the right place to start, also your problem seems to be more related to Protobuffs, why do you want to implement it with Protobuffs, what advantage does it have over just reusing the existing solution? Just curious.

<!-- gh-comment-id:2217374870 --> @MayurSMahajan commented on GitHub (Jul 9, 2024): Discord would be the right place to start, also your problem seems to be more related to Protobuffs, why do you want to implement it with Protobuffs, what advantage does it have over just reusing the existing solution? Just curious.
Author
Owner

@nebiyuelias1 commented on GitHub (Jul 9, 2024):

Discord would be the right place to start, also your problem seems to be more related to Protobuffs, why do you want to implement it with Protobuffs, what advantage does it have over just reusing the existing solution? Just curious.

Honestly it's the way things work at the moment and implementing the feature request requires the modification I described.

<!-- gh-comment-id:2217396581 --> @nebiyuelias1 commented on GitHub (Jul 9, 2024): > Discord would be the right place to start, also your problem seems to be more related to Protobuffs, why do you want to implement it with Protobuffs, what advantage does it have over just reusing the existing solution? Just curious. Honestly it's the way things work at the moment and implementing the feature request requires the modification I described.
Author
Owner

@gustamor commented on GitHub (Aug 3, 2024):

@nebiyuelias1 How's it going?

The custom color feature for the cursor and selection in the workspace settings adds an icon to the color text box. Clicking this icon opens the color picker, which returns the corresponding color code and places it in the text box. This action does not alter any other elements; it simply updates the text box value with the selected color code and submits it in the same way as if the user had manually entered the code. I think this might work the same way.

<!-- gh-comment-id:2266662022 --> @gustamor commented on GitHub (Aug 3, 2024): @nebiyuelias1 How's it going? The custom color feature for the cursor and selection in the workspace settings adds an icon to the color text box. Clicking this icon opens the color picker, which returns the corresponding color code and places it in the text box. This action does not alter any other elements; it simply updates the text box value with the selected color code and submits it in the same way as if the user had manually entered the code. I think this might work the same way.
Author
Owner

@nebiyuelias1 commented on GitHub (Aug 3, 2024):

@nebiyuelias1 How's it going?

The custom color feature for the cursor and selection in the workspace settings adds an icon to the color text box. Clicking this icon opens the color picker, which returns the corresponding color code and places it in the text box. This action does not alter any other elements; it simply updates the text box value with the selected color code and submits it in the same way as if the user had manually entered the code. I think this might work the same way.

Hi the situation is different in this context. More info about the problem could be found here on discord: https://discord.com/channels/903549834160635914/905299371485188137/1260206983122915388.
I didn't understand how the proto buff modifications should work so I haven't made much progress on this one. Would love to get some help!

<!-- gh-comment-id:2266714922 --> @nebiyuelias1 commented on GitHub (Aug 3, 2024): > @nebiyuelias1 How's it going? > > The custom color feature for the cursor and selection in the workspace settings adds an icon to the color text box. Clicking this icon opens the color picker, which returns the corresponding color code and places it in the text box. This action does not alter any other elements; it simply updates the text box value with the selected color code and submits it in the same way as if the user had manually entered the code. I think this might work the same way. Hi the situation is different in this context. More info about the problem could be found here on discord: https://discord.com/channels/903549834160635914/905299371485188137/1260206983122915388. I didn't understand how the proto buff modifications should work so I haven't made much progress on this one. Would love to get some help!
Author
Owner

@annieappflowy commented on GitHub (Jan 3, 2025):

duplicate #5570

<!-- gh-comment-id:2568769759 --> @annieappflowy commented on GitHub (Jan 3, 2025): duplicate #5570
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#2445
No description provided.