jake.fun
he/they • https://anothermachine.info • dev advocate • algorithmic music • alternative uses of web technology • reading non fiction • chicago
172 posts
711 followers
596 following
Prolific Poster
Conversation Starter
comment in response to
post
approved
comment in response to
post
CC can only read the component property layer and does not have read access to the style layer (variables or raw values). It also cannot modify your design file at all. Plugins are often used to create and modify items inside of Figma programmatically. Design linting is something I'm interested in!!
comment in response to
post
A new variant in Figma still requires engineering in code, not just for the property, but style too. Similarly, CC can't modify the design via code. CC doesn't replace DS engineering, it makes the DS easier to use for devs who have a lot of code to implement. LMK if that's unclear!
comment in response to
post
Code Connect isn't bi-directional. It translates component language in Figma to the expected code component language which is often similar but unique. Knowing which configuration of which component you're looking at can be a challenge for many devs consuming a design file. CC simplifies this.
comment in response to
post
Thanks! we have some annotations examples here: github.com/figma/plugin...
our docs are really good too and easy to search! www.figma.com/plugin-docs/...
comment in response to
post
you gotta have edit access to the file you’re running api code on
comment in response to
post
i had a three year old project go off like a month ago. bit of a nailbiter…
comment in response to
post
getting in and out of hn homepage unscathed is quite a rush
comment in response to
post
thank you for this!
comment in response to
post
there are still many folks doing authoritative and respectable work, i just can’t help but feel we have swapped out a sense of community that naturally rises out of shared curiosity and awe for transactional relationships that require continual renewal and appeasement.
comment in response to
post
i keep it external too. it’s hard to keep track of what i’m doing when it’s constantly present.
comment in response to
post
well the simple answer is that i want to stop using large dependencies too lol
comment in response to
post
It's tiny, but can be rendered nicely with image-rendering: pixelated in CSS. Anyway, here is the configuration of the instrument in that video.
comment in response to
post
that image floating in top is actually the save format. this is a static web application without a backend. unless you consider png images to be a backend…
comment in response to
post
god grant me the patience of a united club worker keeping the area around the ladled ranch dressing bucket presentable
comment in response to
post
it’s a lot more complex than where i got in that video too…still trying to find the time to get it to that first release.