Re: [community-group] Legacy color (#137)

> 1. What should the editing flow/color picking UX be?

Checking if a color token is out of gamut or has an unknown color space is trivial.
Each tool can scan a token file for tokens it can not represent faithfully or edit without altering the result.

If it is a translation tool this could be a warning that can be silenced.

For design tools this is problematic and I would see this as a destructive action.
Following usual UX patterns the user would be given a prompt to explain and warn about the destructive action.

> 2. When saving/exporting edited color tokens, what sort of prompts would you expect in relation to potential data-loss?

_see 1._

> 3. What should the exported data look like (considering the user may have picked an sRGB color, overwriting a P3 color)?

Can you clarify or give a concrete example?
I do not follow the question.

> 4. What about people working on monitors that don't cover sRGB? What should their editing experience be?

This is a problem that exists today and will continue to exist.
Even if we use hex and limit to sRGB, this problem will exist as even this smaller color space can not always be fully represented.

-------------

Aside from these points I still do not understand why it is not possible to use a data format that has a clear update path?

I don't want to have some legacy code that checks if `$value` for `$type: color` is of type `string`.

```json
{
  "color-token": {
    "$type": "color",
    "$value": {
      "colorSpace": "sRGB",
      "channels": [1, 0.5, 0],
      "alpha": 1
    }
  }
}
```

The questions that surface from using hex are almost exactly the same as those you have for color spaces :)

- are tools expected to support v1 forever? (both yes and no are problematic)
- what if you open a file with old version in a new tool and save it?
- what if you open a file with a new version in an outdated tool?


-- 
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/137#issuecomment-1175786660 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 6 July 2022 05:08:25 UTC