51–55 of 55 posts
Folks check this out a clear alternative to responsive design and intention.js ( 100% server side .. easy to follow) http://www.codewithsnow.com/portal/snow/gettingstarted I am downloading the tomcat version now ….
Earlier quoted context omitted.
No. The entire purpose of responsive design is that it adapts to the client that is being used to view it.
Why can't this adaptation happen on the server? Client tells server what the resolution possibilities are ("the current browser size is X by Y, and my screen size (and thus maximum browser size) is W by Z), and server gives back only styles relevant to that size. On mobile devices where the browser is always fullscreen, that means a maximum of two layouts (horizontal, vertical).
Nice emulator: http://codewithsnow.com/emulator/
Reading the comments, I guess I am the only guy who still doesn't believe in responsive design in the first place. I just haven't seen a really good implementation of it from a behavior perspective, regardless of what framework or technique is used under the hood. I mean, stacking a three column desktop layout into a single long column for phones is not desirable to me. And, when I view a full desktop site on a phone…
I appreciate your concerns about responsive design, namely the logistical and performance-related issues of creating a separate user experience for mobile devices. I'd like to add that responsive design doesn't have to be an annoying exercise in which developers try to flatten a full-featured site into one column. On the contrary, they can begin by developing a site that works well for mobile, then expand it into a D…
I probably should have been clear that the one column thing was just an example. I agree that there is certainly more to responsive design than that, else it would be much easier!
But, what you mentioned with regard to being more thoughtful about the design and distilling it to its minimalistic essence is partly where I was going, except to a different conclusion. That is, if such a clean, focused design can be achieved, then what results is a Web app that could likely work well across devices.
But, if that minimalistic design leaves much to be desired on the desktop (i.e. a remarkably better experience can be delivered because of the additional available real estate, well then we are likely talking about a fundamentally different design. In that case, I say build it out separately vs. trying to have each page, CSS, etc. pull double-duty.
>Developing a minimalistic version of my Web app in the beginning helped me to focus [...] it's a useful aspect of responsive design
Good point. But, I think that's more a side effect of mobile-first than responsive design.
Earlier quoted context omitted.
there's a method intent.add you pass your node to and it will perform all manipulations on it and keep it registered for any future changes.
Cool, thanks. I assume there's an intent.remove as well? Also is there a more in depth documentation on this or are you on the dev team?
That's interesting, but I'd expect their website to actually use their own product appropriately when viewing from my mobile devices. The "examples" page works, but isn't really in a well designed format - font headings are too large, text is pushed all the way to the far left without a single pixel margin causing it to look like the page should scroll horizontally, etc... I like the concept of what they're doing, bu…
What device is looking wonky? It's much more likely the CSS just needs a fix. It sounds like the library itself is working correctly.