61–70 of 84 posts
These use a lot of empty divs. It's no different in approach to the "twitter fail whale in css" experiment of last year.
I'll be impressed when someone can build a logo out of CSS... semantically .
I hate to be "that dick" so let me first say that this is damn impressive stuff; kudos to the authors for some serious CSS wizardry! It's also completely and totally useless. The person / people who did this are obviously talented and have a lot of expertise. I'd really rather see people with this level of ability contributing meaningful, useful tools / techniques to the community rather than seeing this type of post…
Also called hacking.
Earlier quoted context omitted.
The rendering of data is data itself. We structure databases semantically for backend developers. Why shouldn't we structure display markup semantically for frontend developers?
> The rendering of data is data itself. Only if you have a poor system of sharing data, one that necessitates the rendering to be the data. Why put that inflexible requirement upon yourself? We have plenty of renderings that are not supposed to be data (i.e mechanically readable) by themselves, from graphical UIs to paper printouts. > We structure databases semantically for backend developers. > Why shouldn't we stru…
That's not really true, though. The viewer is the target audience of the display output, not the markup. The target of your markup is either someone technically minded (who would do a 'view source') or some sort of crawler that is trying to derive semantic sense from your document.
In that context, semantic markup makes total sense. Part of me is still disappointed that using XML+XSL for web pages never took off- implementation nightmares aside, separating page data and page presentation is an awesome concept.
Earlier quoted context omitted.
It's also completely and totally useless Not really. A CSS logo would be useful for performance issues and overall page rendering speed. A CSS animated logo, such as the Atari example, even moreso than a Flash / JS counterpart. CSS renders more quickly than images, and definitely more quickly than embedded Flash.
CSS is the wrong tool for the job. Your example would be better served (and easier to maintain) with SVG or Canvas.
I hate to be "that dick" so let me first say that this is damn impressive stuff; kudos to the authors for some serious CSS wizardry! It's also completely and totally useless. The person / people who did this are obviously talented and have a lot of expertise. I'd really rather see people with this level of ability contributing meaningful, useful tools / techniques to the community rather than seeing this type of post…
It's also completely and totally useless Not really. A CSS logo would be useful for performance issues and overall page rendering speed. A CSS animated logo, such as the Atari example, even moreso than a Flash / JS counterpart. CSS renders more quickly than images, and definitely more quickly than embedded Flash.
It also depends heavily on the complexity of the logo and the painting implications. To say simply that "CSS will be more performant" is categorically incorrect.
I hate to be "that dick" so let me first say that this is damn impressive stuff; kudos to the authors for some serious CSS wizardry! It's also completely and totally useless. The person / people who did this are obviously talented and have a lot of expertise. I'd really rather see people with this level of ability contributing meaningful, useful tools / techniques to the community rather than seeing this type of post…
It shows off what a clever person can achieve by tinkering with a system Also called hacking .
I'm kind of bummed that most of these are thoroughly broken in Opera, and I wonder whether it's the CSS that's broken or whether Presto is rendering them wrong.
Maybe a dumb question from someone who isn't proficient with CSS -- but if you can render these as vector images, can't you autogenerate the CSS for them? And the reason I even ask is I feel like I could draw all of these logos pretty well with Illustrator, but couldn't just sit down in a text editor and make these logos with CSS.
This is especially the case with buttons. Photoshop is confusing, CSS3 less so.
I hate to be "that dick" so let me first say that this is damn impressive stuff; kudos to the authors for some serious CSS wizardry! It's also completely and totally useless. The person / people who did this are obviously talented and have a lot of expertise. I'd really rather see people with this level of ability contributing meaningful, useful tools / techniques to the community rather than seeing this type of post…
I mean, one could easily argue that delivering movies and TV shows to people via the internet is also completely and totally useless, couldn't they? So yeah, you are being that dick.
Earlier quoted context omitted.
The rendering of data is data itself. We structure databases semantically for backend developers. Why shouldn't we structure display markup semantically for frontend developers?
> The rendering of data is data itself. Only if you have a poor system of sharing data, one that necessitates the rendering to be the data. Why put that inflexible requirement upon yourself? We have plenty of renderings that are not supposed to be data (i.e mechanically readable) by themselves, from graphical UIs to paper printouts. > We structure databases semantically for backend developers. > Why shouldn't we stru…
By that line of reasoning, why should a semantically-structured database matter? The website viewers never see that, either.
Unless the reason you care about semantics in your database is for ease of development. In which case, all the front-end developers you might work with in the future would thank you for thinking of them when you output your markup.