Open CableGuy67 opened 5 years ago
I'm thinking of allowing the user to save a color palette which they can import / export between patterns. How does 16 colors sound per palette?
So you can refer to them as 0-F? ;)
16 is a ton. Maybe 16 for the main working palette would be great. But what would work out best if you can use your saved palettes to import color settings into your working palette. That way, the number that each hold (apart from the working one that is) becomes irrelevant so long as you can have how ever many palettes you like.
For example: I have a book that I have made up with different threads. Each page has space for 10 items. I sort of group them but as new thread types come in you like to move them around. I'd rather have 20 individual palettes that I could name (or 30 or 50) that were saved in the same way as a pattern. The system doesn't care about the saved palettes except when I am moving a color from my saved palette to my working palette.
I hope this makes a little bit of sense. Also, I like F as a number of items on a palette but I'm a bit of a nerd. :P
I suppose for that joke to work I should have said I like 0x10 to be truly pedantic.
Thanks! I'll see what I can do.
Powers of 2 are always good.
The Color Picker/Color Books/Restore Defaults thing is great. It works perfectly for selecting and modifying colors.
Each time a new pattern is started you get the default colors. I would propose the ability to create and store (perhaps in the user account) a much expanded number of custom colors. These colors should also be able to be named to help with retrieval via some sort of picker and/or search mechanism. In the very least that would allow people with an account to save their own custom colors.
On a larger note would be to make those colors have the ability to be part of a global color picker. For example, if I were to come up with color info for every 8/2 mercerized cotton thread by Butterfly threads (lot number withstanding) it would be nice to be able to share that info. Probably just something as simply as allowing the creator to make it public. The same sort of thing as can be done with the drafts now.
That's the idea. I've not yet begun to look at the codebase to see how anything is done. This is all from a strictly user viewpoint.