As per the other shot, what do you think you'll do re: the hash? Will someone be able to paste in a hex code? Will they also be able to type in "red", "white" etc and will they remain as words or will they resolve to hex values? All fun usability problems I'm sure you're coming across.
@Tait: I was having this same conversation with @mattrobs earlier today. As for the hash, I was planning on stripping it. Any pasted values with hashes will be stripped on the fly so it wont cause any hassle.
As for the color 'words' — not quite sure yet. On one hand, 'black' and 'white' are handy, but people wouldn't necessarily know to the names of the less popular ones. Also would require unnecessary support (imo) for error handling in the event of a misspelling or someone trying to use 'more sparkle'.
What do you think? Would love to hear your opinion. I personally dont use color names when coding — I tend to stick to hex values or rgba.
Though seriously, I always do color: white; and would expect to do the same here. Although, since I'm using the mouse in this context, it'd probably be easier to do a flick to the corner of the colour well.
Much better, Jesse. This is a lot more coherent and much easier to wrap my head around. I still think the hash would be a good idea because people may want to copy or paste from this text field. If you don't want to put a hash, that works too! In that case, I suggest you remove the space between the color box and the hex value. The space makes me feel as if something's missing. :P
9 Responses
This feels much more coherent to me.
almost 2 years ago
looks so simple, but probably was a hell of a lot of work to get it just right. ;-)
almost 2 years ago
That makes a lot more sense. Good idea to upload the GIF. ;)
Will it be possible to save colours for later re-use, or to define set palettes?
almost 2 years ago
As per the other shot, what do you think you'll do re: the hash? Will someone be able to paste in a hex code? Will they also be able to type in "red", "white" etc and will they remain as words or will they resolve to hex values? All fun usability problems I'm sure you're coming across.
almost 2 years ago
@Mark: You'll just have to wait and see... :D
@Tait: I was having this same conversation with @mattrobs earlier today. As for the hash, I was planning on stripping it. Any pasted values with hashes will be stripped on the fly so it wont cause any hassle.
As for the color 'words' — not quite sure yet. On one hand, 'black' and 'white' are handy, but people wouldn't necessarily know to the names of the less popular ones. Also would require unnecessary support (imo) for error handling in the event of a misspelling or someone trying to use 'more sparkle'.
What do you think? Would love to hear your opinion. I personally dont use color names when coding — I tend to stick to hex values or rgba.
almost 2 years ago
I won't use an app that doesn't support the
more-sparklecolor keyword. How else will it pop?!almost 2 years ago
Though seriously, I always do
color: white;and would expect to do the same here. Although, since I'm using the mouse in this context, it'd probably be easier to do a flick to the corner of the colour well.almost 2 years ago
Much better, Jesse. This is a lot more coherent and much easier to wrap my head around. I still think the hash would be a good idea because people may want to copy or paste from this text field. If you don't want to put a hash, that works too! In that case, I suggest you remove the space between the color box and the hex value. The space makes me feel as if something's missing. :P
almost 2 years ago
Love it, I think this is way better than the other version. :D
almost 2 years ago