Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Font Awesome 4 released

fontawesome.io

Post reply on HN
Print view View original

91–97 of 97 posts

Re: Font Awesome 4 released

#91

Post by anton-107 »

leeoniya wrote: post #19

370 icons is nice, but what i really want is a tool that lets me put together a smaller subset from multiple icon fonts that only has what my app needs. A global font-icon library from which to assemble this subset would be ideal. These collections are trying to cater to everyone by growing in size when the better solution here is a modularizer.

What i would add to this: this tool has to be command-line tool. Ideally: declare the names of the icons you are using in some sort of a config file and build a font/svgs/images for all of them

Re: Font Awesome 4 released

#93

Post by ris »

yackob03 wrote: post #85
ris wrote: post #79

What I see on that page: one hell of a lot of unicode placeholders and not much else. We don't all agree with a site's font choices. And at least img made an attempt at semantic meaning and accessibility with alt= attributes. The failure modes for img are actually quite good. There's no such concern in the minds of those who gave birth to icon fonts.

Ligature symbols actually addresses this. there just aren't enough of them for my needs. http://kudakurage.com/ligature_symbols/

I must admit that's actually quite a cool solution.

I'm still not totally convinced by font abuse though.

Re: Font Awesome 4 released

#95

Post by rrrx3 »

fortawesome wrote: post #24
skore wrote: post #21

Seems like a lot of people don't like the namespaces changes. I actually really like this! I suppose it's cumbersome even if you're building a project where you have full control. Then again - come on, we're talking about search&replace for 10 minutes here. And in more complex projects, you should have had a flexible function to handle icons anyways. Why I really, really like it: If you're building something in a nam…

It's also customizable in the LESS or SCSS as a variable. Want to go back to the icon-* prefix? No problem.

Thanks for that foresight. I wasn't pleased about the namespace changes, but this makes it tolerable.

Re: Font Awesome 4 released

#96

Post by ds9 »

ris wrote: post #79

What I see on that page: one hell of a lot of unicode placeholders and not much else. We don't all agree with a site's font choices. And at least img made an attempt at semantic meaning and accessibility with alt= attributes. The failure modes for img are actually quite good. There's no such concern in the minds of those who gave birth to icon fonts.

Same here( "a lot of unicode placeholders" ). Can anyone clarify what would make these visible with Firefox 24 on Windows? (Same result for me with Iceweasel, but it's a few versions behind)

The site says JS is not required, and turning it on didn't help. FF 24 is just about the latest. What browser is this intended for?

Re: Font Awesome 4 released

#97

Post by iSnow »

ds9 wrote: post #96
ris wrote: post #79

What I see on that page: one hell of a lot of unicode placeholders and not much else. We don't all agree with a site's font choices. And at least img made an attempt at semantic meaning and accessibility with alt= attributes. The failure modes for img are actually quite good. There's no such concern in the minds of those who gave birth to icon fonts.

Same here( "a lot of unicode placeholders" ). Can anyone clarify what would make these visible with Firefox 24 on Windows? (Same result for me with Iceweasel, but it's a few versions behind) The site says JS is not required, and turning it on didn't help. FF 24 is just about the latest. What browser is this intended for?

Configure your NoScript options and uncheck "Forbid @font-face" (under Embeddings) and you are done.
Post reply on HN