ofbiz-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Byers <r.ted.by...@gmail.com>
Subject Re: getting screen.width in ftl
Date Thu, 17 Jan 2013 16:55:11 GMT
Hi Paul,

On Thu, Jan 17, 2013 at 4:48 AM, Paul Piper <pp@ilscipio.com> wrote:
> I would not recommend to do anything with Javascript in this case. Responsive
> design is the most obvious solution and should be the most preferrable.

And my first instinct would have been to use js, perhaps because I
have recently been studying the relatively new features in HTML5 that
seem intriguing.

> There are alot of resources available that can show you how to do this
> properly for the different standard solutions. In adddition to your own
> solution, you should take care of more than just the max-width:800 sized
> versions and focus on the different standards that are available.
Would you care to share your favourite resources?  Maybe I picked the
wrong search parameters, but when I search the web for this info, the
signal to noise ratio is abysmal.  :-(

> If you were to go the alternative route, using js would not be an option,
> since you do run js after the initial page load, so js based redirects would
> only increase the heap. Rather, you could try to get the client from request
> header and redirect based on that or, preferably, use your actual
> httpd-server to handle the redirect.
OK, I can easily get the client from the request header, but, can you
shed light on the Apache rewrite rules you show below, in terms
suitable for a guy that can write code in a number of programming
laguages but for whom this kind of web server administration seems
like magic?  I have such trouble with the configuration file for
Apache's web server that I have yet to figure out how to force all
http requests (or all requests for a specific resource) to be resent
using https.  :-(

> With Apache you could use the following:
> RewriteEngine On
> RewriteBase /
> RewriteCond %{HTTP_USER_AGENT}
> android|avantgo|blackberry|blazer|compal|elaine|fennec|hiptop|iemobile|ip(hone|od)|iris|kindle|lge\
> |maemo|midp|mmp|opera\ m(ob|in)i|palm(\
> os)?|phone|p(ixi|re)\/|plucker|pocket|psp|symbian|treo|up\.(browser|link)|vodafone|wap|windows\
> (ce|phone)|xda|xiino [NC,OR]
> RewriteCond %{HTTP_USER_AGENT}
> ^(1207|6310|6590|3gso|4thp|50[1-6]i|770s|802s|a\
> wa|abac|ac(er|oo|s\-)|ai(ko|rn)|al(av|ca|co)|amoi|an(ex|ny|yw)|aptu|ar(ch|go)|as(te|us)|attw|au(di|\-m|r\
> |s\
> )|avan|be(ck|ll|nq)|bi(lb|rd)|bl(ac|az)|br(e|v)w|bumb|bw\-(n|u)|c55\/|capi|ccwa|cdm\-|cell|chtm|cldc|cmd\-|co(mp|nd)|craw|da(it|ll|ng)|dbte|dc\-s|devi|dica|dmob|do(c|p)o|ds(12|\-d)|el(49|ai)|em(l2|ul)|er(ic|k0)|esl8|ez([4-7]0|os|wa|ze)|fetc|fly(\-|_)|g1\
> u|g560|gene|gf\-5|g\-mo|go(\.w|od)|gr(ad|un)|haie|hcit|hd\-(m|p|t)|hei\-|hi(pt|ta)|hp(\
> i|ip)|hs\-c|ht(c(\-|\ |_|a|g|p|s|t)|tp)|hu(aw|tc)|i\-(20|go|ma)|i230|iac(\
> |\-|\/)|ibro|idea|ig01|ikom|im1k|inno|ipaq|iris|ja(t|v)a|jbro|jemu|jigs|kddi|keji|kgt(\
> |\/)|klon|kpt\ |kwc\-|kyo(c|k)|le(no|xi)|lg(\
> g|\/(k|l|u)|50|54|e\-|e\/|\-[a-w])|libw|lynx|m1\-w|m3ga|m50\/|ma(te|ui|xo)|mc(01|21|ca)|m\-cr|me(di|rc|ri)|mi(o8|oa|ts)|mmef|mo(01|02|bi|de|do|t(\-|\
> |o|v)|zz)|mt(50|p1|v\
> )|mwbp|mywa|n10[0-2]|n20[2-3]|n30(0|2)|n50(0|2|5)|n7(0(0|1)|10)|ne((c|m)\-|on|tf|wf|wg|wt)|nok(6|i)|nzph|o2im|op(ti|wv)|oran|owg1|p800|pan(a|d|t)|pdxg|pg(13|\-([1-8]|c))|phil|pire|pl(ay|uc)|pn\-2|po(ck|rt|se)|prox|psio|pt\-g|qa\-a|qc(07|12|21|32|60|\-[2-7]|i\-)|qtek|r380|r600|raks|rim9|ro(ve|zo)|s55\/|sa(ge|ma|mm|ms|ny|va)|sc(01|h\-|oo|p\-)|sdk\/|se(c(\-|0|1)|47|mc|nd|ri)|sgh\-|shar|sie(\-|m)|sk\-0|sl(45|id)|sm(al|ar|b3|it|t5)|so(ft|ny)|sp(01|h\-|v\-|v\
> )|sy(01|mb)|t2(18|50)|t6(00|10|18)|ta(gt|lk)|tcl\-|tdg\-|tel(i|m)|tim\-|t\-mo|to(pl|sh)|ts(70|m\-|m3|m5)|tx\-9|up(\.b|g1|si)|utst|v400|v750|veri|vi(rg|te)|vk(40|5[0-3]|\-v)|vm40|voda|vulc|vx(52|53|60|61|70|80|81|83|85|98)|w3c(\-|\
> )|webc|whit|wi(g\ |nc|nw)|wmlb|wonu|x700|xda(\-|2|g)|yas\-|your|zeto|zte\-)
> [NC]
> RewriteRule ^$ http://m.ilscipio.com [R,L]
As little as I understand how the above works, or what it means, I
guess I have another question which is, would this mean a separate
suite of presentation layer files for each kind of client?  Or is
there a way to have a single suite of presentation layer files that
just adapts to what the client is?



View raw message