The designer of this FontStruction has chosen not to make it available for download from this website by choosing an “All Rights Reserved" license.
Please respect their decision and desist from requesting license changes in the comments.
If you would like to use the FontStruction for a specific project, you may be able to contact the designer directly about obtaining a license.
11 Comments
I think S could use a couple more pylons (top and bottom) to balance the color of that character.
The usability has just increased by 1000%.
Fav letters are B,F,M,W,8.
I'm really shocked I like M & W, as I'm not a fan of monospaced, but these look like they're shaking hands or arm wrestling. Have you thought of having diagonal cutouts on the zero, and having the O & S as a target cutout.
Also the thin line at the end of the glyphs is messing up the line spacing. 9.5/10
@djnippa: minimum is not about usability. The idea with the chevrons was a split-second decision while I felt that I have some creative energy early in the morning. The purpose of the fs was to do the arrows, not the letters. The letters were added (subtracted!) because the arrows by themselves looked silly. The shapes of the letters came about because there were a lot of dots and, unlike beate, I have only a limited capability to extract shapes from a solid brick grid (@meek: see below). This was a very utilitarian typeface building process. The glyphs were just a necessity. The only think I attempted with the letters was to try an not do standard stencilling. fs Scroll was more a minimum fare; fs Scroll (Not) is more of thalamic's territory.
Thanks, as always for the likes. I was also surprised at your like for a monospaced font. But with the arrows needing to fit one into another with periodic regularity, there was no other option but to make this fs monospaced. Ah, limitations! How I love them so!
Having said that, I'd suggest two modifications to the fontstructor (with the help of reference image below):
1. Make the guidelines a bit more visible.
2. Make the guidelines lockable so that once they are in place, you don't inadvertently move them about.
3. (Yes, 3, because this is a non-guide request) The copy-paste-move grid placement is a bit too tight. Meaning, when you move a block of bricks from one place to another, you have to place them in the exact grid blocks otherwise they jump one grid line over. This reminds me of early C64 platform games where you had to nudge the sprites to the exact pixel to jump or whatever. Later games relaxed the tolerance between sprite collision and sprite-to-background detection. In short, the move tolerance in the previous fontstructor worked better. Thanks.
Bravo
Please sign in to comment.