CSS for icons is like HTML tables for markup. You have a path, split it to pieces you can represent with CSS using the methods you consider acceptable and draw a shape using ::before and ::after pseudo-elements.
Sure, those icons were carefully hand-crafted. This requires a lot of patient work, and this is admirable.
Yet, we have SVG for vector graphics. Embed it with data: URIs (I believe browsers who support CSS3 transforms can display SVG backgrounds) and that's it.
Also, the PNG image is 24 bits per channel, obviously unnecessary for this kind of project. Taken down to 8 colors it loses no effective detail, and the size is dropped to 2.6 kb, or perhaps smaller after gzip.
Not saying this particular approach is practical, but if we really could arrive at a practical solution for icons that left the HTML that clean, it'd be great.
Loving this. Unicode has some awesome symbol dingbats (not just arrows, even weather symbols, coffee cups and the likes) for UI icons too but this goes a step further and is more stylish (plus Android fonts don't have most dingbats, not even the arrows -- not sure about iOS).
In principle it's a good idea. There is a problem with this particular set, though. The icons are represented by ordinary characters like "A", which is confusing for users without webfonts, or on screenreaders. Some of this can be fixed by remapping the font to more appropriate characters, but you may not want to go to that much trouble.
any reasonably complete unicode font should already include many of those glyphs. for the glyphs that aren't in the unicode standard, there are private use areas that could accommodate them.
Yeah, as the opening paragraph of the article says, I did this just as 'an exercise in creative problem solving and working within constraints. This is not a "production ready" CSS icon set.'
Hopefully it's clear that it's not being presented as something to be used in production or instead of SVG/other more appropriate technologies.
I see no reason why you couldn't use canvas to generate icons as data URI's. Each icon could then be represented as a set of canvas drawing instructions, that could be pre-rendered, scaled for different devices/uses, cached, etc. I think that would be a better long-term solution.
IE8 does not support canvas. Raphaël.js is there for a reason, and one of them is to abstract developers from implementation details and let them just say "I want this graphics here".
Hardly. Having worked on intranet applications I know first-hand how critical performance is. One on end of the scale you have very small companies, sharing your apps infrastructure with their timesheeting, invoicing and other app servers. On the other end you have companies like Shell, with a user base of over 110,000 employees. All their servers are hosted in the Hague.
CSS for icons is like HTML tables for markup. You have a path, split it to pieces you can represent with CSS using the methods you consider acceptable and draw a shape using ::before and ::after pseudo-elements.
Sure, those icons were carefully hand-crafted. This requires a lot of patient work, and this is admirable.
Yet, we have SVG for vector graphics. Embed it with data: URIs (I believe browsers who support CSS3 transforms can display SVG backgrounds) and that's it.