Of all the things that AngularJS makes easy, files uploads aren’t one of them. You can grab some OPC (other peoples’ code) or ignore IE9.
EDIT 4/2: This one does not use Flash, so that’s good.
Lately, I’ve been spending alot of time in coding in AngularJS, in my case; porting existing functionality from an existing application. One challenge has been keeping the bulk of the application intact, while introducing an Angular architecture on top. Sometimes, it’s just not feasbile to rewrite everything and one must take a modular approach.
Thankfully, the Angular team provides us angular.bootstrap.js ( which has nothing to do with that twitter boilerplate thing)…
After jsConf this year, I took the family to Disney World (what a guy, right?). One ride that I had never been on before was the Carousel of Progress; a journey through time that celebrates change. Professionally, I felt like I’ve been on that ride without being allowed to get off for the last few years.
I’m not a micro-optimization troll (there’s plenty of that out there), but it’s shocking how some devices perform with the simple things we all take for granted. I would argue that for most devices, processing and latency are more important than Kb size.
So let’s take a look…
Update: Refactored to remove namespacing.
A lot has been said about Responsive Design lately. It’s primary a design movement, but the real problem it tries to solve is making content “flow like water.” To me it’s not about media queries, or 100% image widths, it’s about: one url, one codebase, and future-proofing new capabilities to maximize user experience.
Therefore, I give you: Responsive Modules.
I was recently asked to put together a list of the most important issues in UI development on the web today and here’s what I came up with:
Well now that I got your attention…
When looking for a good strategy for implementing a responsive design, web devs are bombarded with tons of techniques, libraries, polyfills, and workarounds. Most of the time, we don’t need them.