ofbiz-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Skip" <s...@thedevers.org>
Subject RE: getting screen.width in ftl
Date Thu, 17 Jan 2013 21:26:24 GMT
Thanks to everyone for this discussion.  Paul, I agree with Teds comment
"the signal to noise ratio is abysmal" when searching for responsive design.
I too would love to know your favorite resources.

Nick, thanks again for your input.  In my view, your approach for simple
content (CSS hidding of certain elements) is ideal.  Have a look at qz.com
to see it in action.

I have spent a month or so on the handheld aspect of this project and have
yet to find anything compelling for responsive design for data entry forms.
Lots of stuff for simple content, but structure form responsive design a
different matter.

What I do know from experience is this, responsive design is more than just
getting the screen to look right on a nearly unlimited number of devices.
Bandwidth, at least in the U.S. for handhelds is abysmal.  Nearly
instantaneous page loads on wired connections take upwards of 30 seconds on
a "fast" 3g connection.  So, loading a bunch of hidden content, especially
images is a bad thing.

Having said that, in my exprerience, @media queries are the absolutely best
choice when it works.

It doesnt work however for complex data entry forms that are used over and
over.  For example, lets say that you have a form with 16 input fields and
maybe a few dropdowns.  If you use jquery-mobile style css, this all comes
as a long list of entries, one per line on a small device.  If you need to
keep some of these fields grouped together, it is VERY difficult to achieve
like this.

Here, javascript was essential for me.  Using javascript, I can use ajax to
retrieve field labels that are abbreviated for small devices and more
informative for desktops.  The choice of those labels is made on the server
based on screen width.  Similiarly, I can use javascript to dynamically set
classes based on the screen size.

Thanks to all

-----Original Message-----
From: Paul Piper [mailto:pp@ilscipio.com]
Sent: Thursday, January 17, 2013 1:48 AM
To: user@ofbiz.apache.org
Subject: Re: getting screen.width in ftl

I would not recommend to do anything with Javascript in this case.
design is the most obvious solution and should be the most preferrable.

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.

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.

With Apache you could use the following:

RewriteEngine On
RewriteBase /

RewriteCond %{HTTP_USER_AGENT}
|maemo|midp|mmp|opera\ m(ob|in)i|palm(\
(ce|phone)|xda|xiino [NC,OR]
RewriteCond %{HTTP_USER_AGENT}
i|ip)|hs\-c|ht(c(\-|\ |_|a|g|p|s|t)|tp)|hu(aw|tc)|i\-(20|go|ma)|i230|iac(\
|\/)|klon|kpt\ |kwc\-|kyo(c|k)|le(no|xi)|lg(\
)|webc|whit|wi(g\ |nc|nw)|wmlb|wonu|x700|xda(\-|2|g)|yas\-|your|zeto|zte\-)
RewriteRule ^$ http://m.ilscipio.com [R,L]

Alternatively for java, you could use

|maemo|midp|mmp|opera\ m(ob|in)i|palm(\

to detect within the request.getHeader("User-Agent").


View this message in context:
Sent from the OFBiz - User mailing list archive at Nabble.com.

View raw message