Dutchcelt's blog

Responsive Images and Web Standards at the Turning Point [del.icio.us]

Probably the most important new development in web technology is the ability to manage images for multiple devices. What we also really need is a way to determine bandwidth. Pushing high pixel ratio images for a tablet over 3G isn't funnny.

Gimme Bar : Front end styleguides [del.icio.us]

This could take up a lot of time! :)

iOS icon corner radii | The Hickensian | Hicksdesign [del.icio.us]

Pixels still matter.

Off Canvas [del.icio.us]

Again we see useful patterns emerging from the mobile space. This is where all the web design innovation is happing at the moment.

UI Patterns For Mobile Apps: Search, Sort And Filter [del.icio.us]

I don't much mobile work. Always seems trivial. That's not to say that it isn't difficult. Good to see more UI patterns become standard in the modile space.

Meteor [del.icio.us]

Not very clear what Meteor can't do. So that does that mean they have lofty ambitions?

Subtle Patterns | Free textures for your next web project [del.icio.us]

It's fun to do it yourself. Great when somebody else does it even better!

impress.js | presentation tool based on the power of CSS3 transforms and transitions in modern browsers | by Bartek Szopka @bartaz [del.icio.us]

Could I use this? Should I?

Weird webkit box-shadow bug [del.icio.us]

So we can't use resolution independent CSS techniques on 'The New iPad". Yeah, Mobile Safari needs an update.

Safely using .ready() before including jQuery - Colin Gourlay [del.icio.us]

Don't want to hack around with AMD loaders and still need fast page loads? This should do the trick very nicely!

Get off my grid!

Grids have become an integral part of design since humans figured out how to print stuff. Grids flourished in the age of reproduction. Discussing the sense and non-sense of grids is something that designers never seem to get tiered of. Responsive web design has added an extra dimension to this discussion. That’s a good thing because any argument for a grid based approach would also need to take responsive layouts in to account. So, how well do grids hold up on the open web?

[read the full article]

Whose prefix is it anyway?

It looks like there is a little bit of a panic about CSS -pre-fixes. Well, that’s just though. It’s a little late to start bitching about it now. It’s not that nobody knew that this was going to happen. History has this habit of repeating itself because we’re all stupid.

[read the full article]

Iconic fonts

The world wide web and images have always made awkward bed fellows. Images are added to the document and are supplemental to text which is the primary mode of communication. So if you want to add an icon you have a number of choices. An image via an html tag, a background via CSS and a typeface via loading an external font. This is where things get mirky.

[read the full article]

The Web Devided

Fluid or rather its new name responsive web design is a typical paradigm of the web. It doesn’t really exist anywhere else, which in of itself is not surprising. Some industries like the publishing industry wants to get in on the act but are still busy defending their turf. They, like many other industries, won’t commit to a new way of thinking.
The old world will not evolve into the new one because they put most of their energy in to what they still have. Incumbents are not saddled by such a burden. The prize is usually theirs for the taking.

[read the full article]

Patterns, breakfast of champions

Creating a website these days is a piece of cake, as simple as a bowl of cereal. It really is. A custom built enterprise behemoth of a web application, however, is a completely different kettle of fish. Each seemingly innocuous decision you make impacts the next and eventually becomes an avalanche of shortsightedness that kills you and the entire village. So, if you’re (un)fortunate enough to be involved a such a large project, watch your step. Getting the basics right might just save you and your kin.

[read the full article]

$CSS

Fronteers ‘11 was great conference, one of the best I’ve been to. Lots of passion and an eyeopener to the direction some seem to be taking the web.

Ruby technology has been making waves in the web dev space for years and it seems that it and others have indirectly influenced the front-end space. CoffeeScript and Sass have, due to their popularity, started the next wave of change. Dart and CSS vars as exhibit A. Great in many respects, however, Front-end is slowly becoming a pure IT job. It’s an easy bet that not everybody will be able to make the transition.

[read the full article]

Elusive Style

Molly’s has a ‘I wish I had…’ post and it reminded me of once wishing I had something like ‘invert’ just like the CSS values ‘auto’ and ‘inherit’.
When I change a background colour I’d like not to have go and change the text colour as well. Usually it’s better to tweak the colour to get the best result but in some cases it doesn’t require such fine tuning.

[read the full article]

Plus one

Just in case you hadn’t heard: The web juggernaut Google has gone all social on us and Twitter has, after Facebook added their status timeline, yet another competitor to contend with.
Twitter’s uniqueness is fading and its focus is shifting. Many users push tweets to Facebook and those that don’t may jump ship to Google+.

[read the full article]

The Web Stack is the next native platform

It is funny and fantastic to see all these dogmatic discussions on ‘Web versus Native’ mobile applications. It’s a strange argument to have because at the moment they don’t actually conflict very much. They do overlap but they’re currently not replacements of each other. I can’t tell you how many times I’ve seen a native app that might as well be web based because it’s not utilising specific hardware API’s. An app is often native because you can have somebody else sell it for you in an app store.

[read the full article]

Class struggle

I’m irked by the fact that I keep running into web sites that use mark-up class names that follow the content language. The web and its mark-up are open to the world, to both humans and machines. For better or for worse in terms of mark-up English is the lingua franca and its metadata should at least also be in English. An ID on the other hand can be part of the content (ie fragment identifier) and when it is it ought to follow the content language of the current document. It can get a little messy, but there is method to the madness.

[read the full article]