Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It's generally much safer to check the browser's <strong>user-agent</strong>, as then you will know whether they are on an Android, iPhone, iPad, iPod, Nokia, ..., and you are given greater flexibility to direct the user from there. I use the following Javascript (probably borrowed from another source):</p> <pre><code> var isMobile = function() { console.log("Navigator: " + navigator.userAgent); return /(iphone|ipod|ipad|android|blackberry|windows ce|palm|symbian)/i.test(navigator.userAgent); }; </code></pre> <p>Screen width is an available technique. I usually see this used with <strong>CSS Media Queries</strong>, changing the content based on "device-width" and "device-height". E.g.</p> <pre><code> @media only screen and (max-device-width: 480px) { /* For small devices, just CSS */ } </code></pre> <p>To go with the technique of screen width / height, this is from <a href="https://developer.mozilla.org/en/DOM/window.screen.width" rel="noreferrer">Mozilla docs</a>:</p> <pre><code> // crude way to check that the screen is at 1024x768 if (window.screen.width &lt; 1000) { // resolution is below 10 x 7 window.location = 'm.mysite.com'; //for example } </code></pre> <p>Here is an in-depth <a href="http://cartoonized.net/cellphone-screen-resolution.php" rel="noreferrer">list of mobile screen resolutions</a>.</p> <p>A few caveats:</p> <ol> <li>If a user goes to <em>www.yoursite.com/events/15</em>, you are going to forward the user directly back to <em>m.yoursite.com</em>. This can be very frustrating when trying to visit a link on a mobile device. You should try to reconstruct the proper URL either by a Javascript library (see <a href="http://millermedeiros.github.com/crossroads.js/" rel="noreferrer">Crossroads.js</a>) or on the server using a redirect.</li> <li><p>As mobile devices get better at rendering and interaction, be aware that oftentimes users may prefer to see the original site instead of the mobile site, full stop. Try to provide a method back to the main site.</p> <p>Hope this all helps you suss out your solution!</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POMobile redirect using screen resolution
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USghayes
    1. USghayes
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMobile redirect using screen resolution
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTu very much for the help. I'm aware of user agents, but user agents come and go I think, not being sure I cover all of them. This is why I am enclined to use screen resolution. For example if a user has some kind of tablet with 1024x 860 resolution, than i dont care about redirecting... it just means he can experience my own site 100%
      singulars
      1. PO
      1. USwebmasters
    2. COThere's nothing wrong with redirecting based on screen width. I would just be very careful about the user flow, esp. when they are coming in from a link (e.g. not to mysite.com, but to mysite.com/something/else). Your solution should work great otherwise. Remember that an iPhone can properly render a page that's 1024px width with proper zooming.
      singulars
      1. PO
      1. USghayes
    3. CONote your link to mobile screen resolutions lists their actual resolution, not what they report via `window.screen.width`. Retina iPhone does "pixel doubling" so it reports 320 pixels wide even though it's actually 640.
      singulars
      1. PO
      1. USEli
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload