Smashing Daily #21: SVG, Clients, Lasers

We need to know what your device testing strategy looks like, we need to know what you know, and we need new ways to work (like using less JavaScript libraries and finding a new design process). At least, that’s what today’s authors tell us. But there’s much more: lasers and fire, for instance. Enjoy!

More please…1
Stephanie Rieger wonders why we don’t read more stories about device testing, and device strategies, especially from bigger companies. I guess one reason is that these companies haven’t really figured these things out yet. Another reason is probably that many companies don’t like to share information (which is a pity, really).

An Ajax-Include Pattern for Modular Content2
One could argue that secondary content—content that’s not directly necessary to fulfill all the needs on a certain Web page—should not be downloaded on a small screen (especially if it’s not directly visible, and only accessible after a long time of scrolling). Instead, a link to that content would be sufficient. Scott Jehl wrote this extended article on the subject, which includes a rather nice jQuery solution that minimizes the amount of HTTP requests needed to load the content on bigger screens. Interesting theory, interesting technique and an interesting solution, too.

A schema3

SVG Animations, CSS Animations, CSS Transitions4
So what happens when you target the same element with a CSS Animation and a CSS Transition at the same time? And what if there’s also an SVG Animation in there somewhere? Dirk Schulze explains what happens in these situations. And he explains how this works with SVG presentation attributes. Complex but interesting stuff. Now, if browser vendors could just started implementing SVG properly…

Publish What You Learn5
Sometimes I may find a clever solution to a complex design issue, or I think of different possible solutions, just to find out that they actually won’t work (I had that with multiple images and media-queries in an SVG file, which sounded like a clever solution, but it just didn’t work out). Louis Lazaris is right in this article when he says that I should have published those findings. He says you should write about what you learn and share it—it’s probably how you learned a lot of what you know about Web development. Excellent advice (just don’t publish too much, as my backlog of articles I need to read is already gargantuan).

Publish what you know6

Let’s not have a JavaScript library anymore7
JavaScript libraries can be easy to use as a developer but there are some serious downsides to them, mostly performance-based. Bran van der Meer explains what these bad parts are and gives a very handy overview of little tools and tiny scripts that you can use to start developing without libraries.

Generate passwords from terminal8
If you want to generate a random password—and you want to look like a real nerd—you might want to use this terminal tip by Thomas Deceuninck. You could also buy a user-friendly tool to do the same thing, instead.

Client Centric Web Design9
If you consider clients to be one of your bigger problems, then this eBook by Paul Boag might help you get over this issue. I haven’t read it yet, but I like the Web page that promotes it (it’s on my reading list, which keeps growing… it’s really starting to get out of hand).

A client10

Throw away Photoshop and be true to your medium11
The title of this article is linkbait, and actually sounds a bit silly since Photoshop is actually used in the design process that James Weiner describes. So forget the title and read the article, especially when you’re working on a user-centric product which is never finished. There are some interesting thoughts about testing, about working together and also the benefits of designing in the browser.

Last Click

Goal celebrations FX12
Some of you might enjoy the Euro 2012 football championships, others couldn’t care less, and many of you probably never even heard of it. But whether you like football or not you will almost certainly love lasers, fire and explosions.

Lasers!13

Previous Issues14

For previous Smashing Daily issues, check out the Smashing Daily Archive15.

Footnotes

  1. 1 http://stephanierieger.com/more-please/
  2. 2 http://filamentgroup.com/lab/ajax_includes_modular_content/
  3. 3 http://filamentgroup.com/lab/ajax_includes_modular_content/
  4. 4 https://blogs.adobe.com/webplatform/2012/03/30/svg-animations-css-animations-css-transitions/
  5. 5 http://www.smashingmagazine.com/2012/03/30/publish-what-you-learn/
  6. 6 http://www.smashingmagazine.com/2012/03/30/publish-what-you-learn/
  7. 7 http://frntndr.com/2012/03/lets-not-have-a-javascript-library-anymore/
  8. 8 http://fronto.be/blog/detail/generate-passwords-from-terminal
  9. 9 http://boagworld.com/books/clientcentric/
  10. 10 http://boagworld.com/books/clientcentric/
  11. 11 http://digital.cabinetoffice.gov.uk/2012/03/29/breaking-down-walls-designing-in-browser/
  12. 12 http://vimeo.com/42976861
  13. 13 http://vimeo.com/42976861
  14. 14 www.smashingmagazine.com/the-smashing-daily-archive/
  15. 15 www.smashingmagazine.com/the-smashing-daily-archive/

Vasilis van Gemert is the Principal Front-end Developer at Mirabeau in The Netherlands and a board member of Fronteers. His aim is to close the gap between design and (front-end) development. He believes the excess of knowledge he has can be better used by others, by more creative and smarter people. You can follow him on Twitter.

Advertising
  1. 00

    No comments have been posted yet. Please feel free to comment first!
    Note: Make sure your comment is related to the topic of the article above. Let's start a personal and meaningful conversation!

Leave a Comment

Yay! You've decided to leave a comment. That's fantastic! Please keep in mind that comments are moderated and rel="nofollow" is in use. So, please do not use a spammy keyword or a domain as your name, or else it will be deleted. Let's have a personal and meaningful conversation instead. Thanks for dropping by!

↑ Back to top