Comments for mpulp http://mpulp.mobi Too long for twitter Tue, 31 May 2011 17:29:37 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Personal hotspot on Verizon iPhone #fail by joeyhttp://mpulp.mobi/2011/05/personal-hotspot-on-verizon-iphone-fail/comment-page-1/#comment-230 joey Tue, 31 May 2011 17:29:37 +0000 http://mpulp.mobi/?p=2323#comment-230 yeah im having this same problem...so wth am i suppose to do because i have been trying for the past half hour and its driving me crazy. yeah im having this same problem…so wth am i suppose to do because i have been trying for the past half hour and its driving me crazy.

]]> Comment on Next steps of Responsive Web Design by John Arne Shttp://mpulp.mobi/2011/05/next-steps-of-responsive-web-design/comment-page-1/#comment-223 John Arne S Sun, 22 May 2011 22:27:30 +0000 http://mpulp.mobi/?p=2197#comment-223 @ Jeremy, I am well aware of your opinions and excellent writings on this topic. Obviously, I am not emphasizing the point enough in the post, but the misunderstanding you refer to IS actually the issue I am addressing. There are enough examples of this way of being "responsive" out in the wild today. Hence my "stupid ... " illustration. Briefly, my main point is that more of the value chain needs to be responsive. Being responsive requires more than just clever css, js and markup magic. @ Jeremy, I am well aware of your opinions and excellent writings on this topic. Obviously, I am not emphasizing the point enough in the post, but the misunderstanding you refer to IS actually the issue I am addressing. There are enough examples of this way of being “responsive” out in the wild today. Hence my “stupid … ” illustration. Briefly, my main point is that more of the value chain needs to be responsive. Being responsive requires more than just clever css, js and markup magic.

]]> Comment on Next steps of Responsive Web Design by Aaron Gustafsonhttp://mpulp.mobi/2011/05/next-steps-of-responsive-web-design/comment-page-1/#comment-222 Aaron Gustafson Sun, 22 May 2011 22:05:22 +0000 http://mpulp.mobi/?p=2197#comment-222 I agree 100% with your assertion that more CMSes need to allow for adapting the code sent over the wire. Some had add-ons that do this. ExpressionEngine, for instance, has <a href="http://www.eec.ms/add-ons/mobile-device-detect" rel="nofollow">a plugin</a> that does server-side detection and allows you to adjust the templates before they are sent to a client. We used that on <a href="http://webstandardssherpa.com" rel="nofollow">Web Standards Sherpa</a> to not only reduce the amount of content sent to mobile devices, but also to preempt the use of media queries in our CSS (so they only came into play on unrecognized small devices). Media queries can be great, but they are definitely no replacement for a responsive CMS. I agree 100% with your assertion that more CMSes need to allow for adapting the code sent over the wire. Some had add-ons that do this. ExpressionEngine, for instance, has a plugin that does server-side detection and allows you to adjust the templates before they are sent to a client. We used that on Web Standards Sherpa to not only reduce the amount of content sent to mobile devices, but also to preempt the use of media queries in our CSS (so they only came into play on unrecognized small devices). Media queries can be great, but they are definitely no replacement for a responsive CMS.

]]> Comment on Next steps of Responsive Web Design by Jeremy Keithhttp://mpulp.mobi/2011/05/next-steps-of-responsive-web-design/comment-page-1/#comment-221 Jeremy Keith Sun, 22 May 2011 22:05:04 +0000 http://mpulp.mobi/?p=2197#comment-221 To suggest that responsive web design automatically involves "tons of markup, css, javascript and content that will not have a function on the mobile device" is to completely misunderstand it. Applying "display: none" to already-downloaded content is *not* what responsive web design is about (it's certainly not progressive enhancement).So I'm afraid that misunderstanding makes what you've written here mostly bollocks. Sorry. To suggest that responsive web design automatically involves “tons of markup, css, javascript and content that will not have a function on the mobile device” is to completely misunderstand it. Applying “display: none” to already-downloaded content is *not* what responsive web design is about (it’s certainly not progressive enhancement).

So I’m afraid that misunderstanding makes what you’ve written here mostly bollocks. Sorry.

]]> Comment on Next steps of Responsive Web Design by John Arne Shttp://mpulp.mobi/2011/05/next-steps-of-responsive-web-design/comment-page-1/#comment-213 John Arne S Wed, 11 May 2011 17:10:43 +0000 http://mpulp.mobi/?p=2197#comment-213 @ John: Cool! This kind of innovation has to come through open-source. Ping me when you have something I can play with :) @ John: Cool! This kind of innovation has to come through open-source. Ping me when you have something I can play with :)

]]> Comment on Next steps of Responsive Web Design by John Arne Shttp://mpulp.mobi/2011/05/next-steps-of-responsive-web-design/comment-page-1/#comment-212 John Arne S Wed, 11 May 2011 17:08:50 +0000 http://mpulp.mobi/?p=2197#comment-212 @ Espen. Yes, fully support your point! The current state of responsive web design is not what we need, but very important in terms of evolution and education. A step we have to go through. @ Espen. Yes, fully support your point! The current state of responsive web design is not what we need, but very important in terms of evolution and education. A step we have to go through.

]]> Comment on Next steps of Responsive Web Design by John Albin Wilkinshttp://mpulp.mobi/2011/05/next-steps-of-responsive-web-design/comment-page-1/#comment-211 John Albin Wilkins Wed, 11 May 2011 16:15:00 +0000 http://mpulp.mobi/?p=2197#comment-211 I completely agree. Performance is only starting to become a concern in the RWD. And I'm glad we are seeing these discussions as we enter the implementation phase.The <a href="http://drupal.org" rel="nofollow">Drupal CMS</a> has a lot that can be leveraged to make the editor/server/cms side of the workflow be less stupid. Image resizing, pre-HTML-rendering item list length manipulation, context-based layout changes… these are all things we can easily do in Drupal. Everything in Drupal is modular. We’re currently in the process of figuring out the best recipe to combine all these ingredients together for a truly delicious RWD implementation. I completely agree. Performance is only starting to become a concern in the RWD. And I’m glad we are seeing these discussions as we enter the implementation phase.

The Drupal CMS has a lot that can be leveraged to make the editor/server/cms side of the workflow be less stupid. Image resizing, pre-HTML-rendering item list length manipulation, context-based layout changes… these are all things we can easily do in Drupal. Everything in Drupal is modular. We’re currently in the process of figuring out the best recipe to combine all these ingredients together for a truly delicious RWD implementation.

]]> Comment on Next steps of Responsive Web Design by espenhttp://mpulp.mobi/2011/05/next-steps-of-responsive-web-design/comment-page-1/#comment-210 espen Wed, 11 May 2011 14:39:25 +0000 http://mpulp.mobi/?p=2197#comment-210 You are pretty much spot on In your analysis of the hype and what the ideal situation looks like. I have just one point to make which is regarding responsive web design. The single most valueable thing from this hype is that _designers_ are realizing they are not designing for Photoshop, but for a web where things never ought to loom exactly the same across devices. This has been an issue for a long time and this hype helps get the knowledge about this across to the design community. Again I totally agree with your points and we can't stop with the web pages, the back-end needs to adapt as well. You are pretty much spot on In your analysis of the hype and what the ideal situation looks like.
I have just one point to make which is regarding responsive web design. The single most valueable thing from this hype is that _designers_ are realizing they are not designing for Photoshop, but for a web where things never ought to loom exactly the same across devices. This has been an issue for a long time and this hype helps get the knowledge about this across to the design community.
Again I totally agree with your points and we can’t stop with the web pages, the back-end needs to adapt as well.

]]> Comment on Smartphones more important than tablets. by Tweets that mention Smartphones more important than tablets.mpulp | mpulp -- Topsy.comhttp://mpulp.mobi/2011/02/smartphones-more-important-than-tablets-2/comment-page-1/#comment-67 Tweets that mention Smartphones more important than tablets.mpulp | mpulp -- Topsy.com Tue, 22 Feb 2011 09:28:37 +0000 http://mpulp.mobi/?p=1191#comment-67 [...] This post was mentioned on Twitter by Jon Arne S., Markus Leutwyler. Markus Leutwyler said: RT @jonarnes: Just #blogged: Smartphones more important than tablets. http://t.co/Z3FstEd via @jonarnes [...] [...] This post was mentioned on Twitter by Jon Arne S., Markus Leutwyler. Markus Leutwyler said: RT @jonarnes: Just #blogged: Smartphones more important than tablets. http://t.co/Z3FstEd via @jonarnes [...]

]]> Comment on App stores vs. the open world wide web by Tweets that mention App stores vs. the open world wide web mpulp | mpulp -- Topsy.comhttp://mpulp.mobi/2011/01/app-stores-vs-the-open-world-wide-web/comment-page-1/#comment-60 Tweets that mention App stores vs. the open world wide web mpulp | mpulp -- Topsy.com Tue, 25 Jan 2011 23:11:23 +0000 http://mpulp.mobi/?p=896#comment-60 [...] This post was mentioned on Twitter by Jon Arne S. and Mobiletech-Holen, Sitaram Shastri. Sitaram Shastri said: great read RT @jonarnes: Just #blogged: App stores vs. the open world wide web http://t.co/u7zg6cd (cc @ppk) [...] [...] This post was mentioned on Twitter by Jon Arne S. and Mobiletech-Holen, Sitaram Shastri. Sitaram Shastri said: great read RT @jonarnes: Just #blogged: App stores vs. the open world wide web http://t.co/u7zg6cd (cc @ppk) [...]

]]>