-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#valueOfTokenNamed: is crappy #156
Comments
@Nyan11 👀 |
We can also use slots for this and I would avoid chaining md sys color shadow |
In Style Dictionary not all pathes are values.
But, |
Therefor the chaining of messages is complicated because certain chains will return nothing. |
The current style sheet rules are like this: self
when: ToPressedLookEvent
write: (self property: #'background-color')
with: [ :e | e valueOfTokenNamed: #'color-primary-pressed' ]
animation: nil. I suggest to do something like this: self
when: ToPressedLookEvent
write: self properties backgroundColor
with: [ :e | e tokens colorPrimaryPressed ]
animation: nil. |
I like chaining of message sends instead of flatten names because it matches a token organization. |
but I have to dig more |
could you talk with marcus because I would like him to think about this? |
Hello, did something happens about this? |
I think not (: |
No but it would be great to use slot to abstract this string base API. |
it is based on a string.
we should kill it.
and use message instead.
example in material design:
md.sys.color.shadow
this could be implemented with:
md sys color shadow
thus, getting the value of a token is simply done through message sending.
Now we need also a kind of infrastructure to specify the object hierarchies.
As an example, Style dictionary would be a good approach
see https://github.com/amzn/style-dictionary
The text was updated successfully, but these errors were encountered: