- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Nov 2022 09:40:11 +0000
- To: public-design-tokens-log@w3.org
> But this means every tool that wants to transform tokens needs to write parsing logic. Parsers, serialisers exist for most languages. More can be created. > Also output may not be css but xml for android or other files e.g. for swift. The same is true for JSON. > This means css properties need to be parsed into a json like shape to re-structure to other languages. The same is also true for JSON. Only JavaScript has a special relationship with JSON. All other programming languages need to parse to their equivalent. ----- I definitely do not mean that CSS is a better or more common data format. It is not. But the CSSWG has done so much work to create ways to record visual/style information in a file. Not building on top of that seems like a waste. Declaring design tokens is something that can be done in CSS and I think it is worth further exploring the benefits of such an approach. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/185#issuecomment-1318353999 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 November 2022 09:40:12 UTC