Advertisements

fs Scroll (Not)

This FontStruction was selected by FontStruct staff.This%20FontStruction%20was%20selected%20by%20FontStruct%20staff.

by minimum
cloned from fs Scroll by minimum


Details

Description:
Clone of fs Scroll.
Stats:
52 characters, 21 downloads
Created:
Mon, 28th November, 2:08 PM 2011
Last Edit:
Sat, 22nd September, 2:13 PM 2012
Tags:
-
Categories:
Rate it:
  • Currently 7.76606
7.8Balanced%20Rating%3A%20%3Cb%20class%3D%22weighted_value%22%3E7.8%3C%2Fb%3E%3Cbr%2F%3EAverage%20Rating%3A%20%3Cb%20class%3D%22rating_value%22%3E8.0%3C%2Fb%3E%3Cbr%2F%3EClick%20for%20more%20information%20about%20this%20rating. 13 votes
sign in to vote.

Discussion

minimum
minimum Wed, 30th November, 2011

I wasn't planning on doing this, but since you asked, here you go, djnippa.


will.i.ૐ
will.i.ૐ Wed, 30th November, 2011

Terrific! I love the interlocking stroke/pylon shapes – W being my favorite of the pack.

I think S could use a couple more pylons (top and bottom) to balance the color of that character.


djnippa
djnippa Wed, 30th November, 2011

Excellent stuff. Now we are talking.
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


minimum
minimum Thu, 1st December, 2011

@will.i.ૐ: You are always kinder to me than I deserve. Thanks. I've started redoing some shapes. Lets see where they end up. Your comments will improve the whole, I'm sure. (PS: I'm attaching an image of the current glyphs because I've noticed that once this is over, the earlier comments just seem confusing to future readers without reference. Hence, the stateshot below.)

@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!

@will.i.ૐ: You are always kinder to me than I deserve. Thanks. I've started redoing some shapes. Lets see where they end up. Your comments will improve the whole, I'm sure. (PS: I'm attaching an image of the current glyphs because I've noticed that once this is over, the earlier comments just seem confusing to future readers without reference. Hence, the stateshot below.)
<br/>
<br/>@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.
<br/>
<br/>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!

minimum
minimum Thu, 1st December, 2011

@meek: Thanks, Rob. Why? For the Extra Guides. Subtracting the letter shapes out of a solid grid of bricks would have been nearly impossible and utterly frustrating without having extra guidelines to, er, guide me along. Very nice addition.

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.

@meek: Thanks, Rob. Why? For the Extra Guides. Subtracting the letter shapes out of a solid grid of bricks would have been nearly impossible and utterly frustrating without having extra guidelines to, er, guide me along. Very nice addition.
<br/>
<br/>Having said that, I'd suggest two modifications to the fontstructor (with the help of reference image below):
<br/>
<br/>1. Make the guidelines a bit more visible.
<br/>
<br/>2. Make the guidelines lockable so that once they are in place, you don't inadvertently move them about.
<br/>
<br/>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.

meek
meek Thu, 1st December, 2011

I'm very glad the extra guides help. 1. I will think on that. I would like an inverted mode for the FontStructor. That might help with guide visibility. 2. Exists! It's in the Menu when you're in Expert Mode. 3. Yes I've heard that from others too. I'll see what I can do.


meek
meek Thu, 1st December, 2011

Congratulations! FontStruct Staff have deemed your FontStruction worthy of special mention. “fs Scroll (Not)” is now a Top Pick.


djnippa
djnippa Thu, 1st December, 2011

I can relate to the pain of your No.3 request. It's driving me nuts. You have to be too accurate. Otherwise it constantly jumps.


minimum
minimum Sun, 15th January, 2012


elmoyenique
elmoyenique Mon, 16th January, 2012

Deliiiicious pict!


Upixel
Upixel Fri, 21st September, 2012

Holy cow! great work!!!
Bravo