Rasmus Andersson

Rasmus Andersson

Design at Figma Joined over 6 years ago

  • 1 story
  • 11 comments
  • 9 upvotes
  • Posted to Figma launches 3.0 with Styles, upgraded Prototyping, and a new Organization tier, in reply to Michal Svoboda , Jun 25, 2018

    Good feedback — thank you! Re defining rounded corners "globally", one solution I've seen around is to define a base "rectangle" component that is used throughout your design instead of a regular rectangle. This allows you to change the corner radius "globally" very easily.

    Here's a demo: https://www.figma.com/file/YtaD1iskeuXPdd5XC6NtPiE8/Rounded-corners-hack

    GIF

    0 points
  • Posted to Interface Font Family, in reply to Jonathan Shariat , Aug 22, 2017

    You're welcome. I believe there should be good, free (and truly free) type faces for common use. It's almost like basic clothing that's not the personality–defining, but instead you wear some interesting details that are (i.e. some other font families can be used to add "personality")

    7 points
  • Posted to Interface Font Family, in reply to Robo Wolf , Aug 22, 2017

    Thank you. I'd love to hear & see how you use it! (I'm @rsms on the Twitters)

    0 points
  • Posted to Interface Font Family, in reply to Erik Shaw , Aug 22, 2017

    The project uses fontbuild, a subproject of Roboto, for parts of the build system. Some glyph outlines from Roboto are also used for placeholder glyphs — glyphs that hasn't been designed yet, to allow using the font even when some glyphs are "missing." (Proper attribution has been given in src/LICENSE for some glyph outlines.txt)

    The plan is to eventually "implement" all glyphs and not need any "placeholder" glyph outlines from Roboto. However, getting there might take a year or so.

    11 points
  • Posted to Interface Font Family, in reply to Ray Sensebach , Aug 22, 2017

    It was not designed for Figma, although we've been testing it out internally for a while and really like it. However, we're sticking with Roboto for now in Figma. Maybe someday we'll switch, maybe we won't. We have a lot of non-English speakers (uhm, writers? :) ) on Figma, so we need a full-featured character set.

    6 points
  • Posted to Interface Font Family, Aug 22, 2017

    Hello. I'm the creator of Interface and here to answer any questions :)

    15 points
  • Posted to AMA: Figma's New Pricing Model, in reply to alfa treze , Apr 06, 2017

    Thank you for the feedback. We're working on improving the team library experience with better search and more organizational features.

    1 point
  • Posted to Components in Figma, in reply to Miguel Solorio , Dec 09, 2016
    • Shared components: We are working on this.
    • Overriding nested instances: This works today — simply select whatever part of a nested instance you want to override. You can either use the layers sidebar, hold cmd to "deep select" (or ctrl on Windows), or double-click until you get to what you want.
    • Padding: This is also possible today. See reply above
    • Would you mind elaborating a bit about what you mean with "Ability to insert existing components without copying/duplicating the original"? Thank you.
    0 points
  • Posted to Components in Figma, in reply to Ben S , Dec 09, 2016

    Not yet, but we are working on making it possible to share components across teams, to be used across documents.

    1 point
  • Posted to Components in Figma, in reply to Weston Thayer , Dec 08, 2016

    Thank you for an insightful comment.

    Addressing some of your feedback, it sounds like we need to work on making constraints a little clearer and easier to use. By default, contents of a component has "scale" constraints which can be thought of as the constraint system maintaining a percentually-equal distance from all four edges. Say you have a component that's 100x100 in size, with a rectangle inside it that sits at position 20,20 and being 60x60 wide. Now, the effective "scale" constraints will be 20% top, 20% right, 20% bottom and 20% left. An instance of that component that is sized to 200x200 px will draw the rectangle with the same distances from its edges (20%, ...), which in this example equals 40 virtual pixels (aka screen points.)

    For the button case, there's a fairly easy way for the author of the button to communicate margins — use constraints on the text label! For instance, if you want the text to always have a 20pt left margin and 10pt right margin, move the text box 20pt to the right of the edge of the component, and make it wide enough so it's 10pt away from the right edge of the component. Now, give the text box right & left, top & bottom constraints. When an instance is resized, the text will wrap to avoid drawing beyond the extremes of the text box, which means that all instances will have 20pt margin on the left and 10pt margin on the right.

    Button constraints

    Does that make sense?

    5 points
Load more comments