Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Updated: Mars 2016</strong></p> <p>Projects are all different, so it's hard to set a global rule that will fit them all. If you're looking for one, here's an example that someone smarter than me came up with and that I've used before:</p> <pre><code>xsmall: (max-width: 479px), small: (max-width: 599px), medium: (max-width: 767px), large: (max-width: 1024px), largeOnly: (min-width: 768px) and (max-width: 1024px), xxl: (min-width: 1200px), tall: (min-height: 780px), </code></pre> <p>Note the lack of references to <strong>devices, screen sizes or orientation</strong> on their names. The size of a <em>'tablet portrait'</em> shouldn't really matter to us as we should try to make things <strong>responsive</strong> and look good on any screen size, not simply <strong>adaptive</strong> to a few screen sizes.</p> <p>Yes, it's important to know the most common screen sizes and avoid crazy media queries, but in the end, your design may start to beg for adjustments at 530px instead of 480px or something like that. So why not?</p> <p>Now, on my <strong>personal preferences</strong>: I keep media queries in mind all the time, but at first I tend to ignore device sizes almost completely. I also prefer the <strong>desktop-first</strong> approach cause I find it easier to adjust layouts to smaller sizes (ie.: removing not so important things from the page, reducing sizes, etc.).</p> <p><strong>Original Answer</strong></p> <p>Some people tend to ignore device sizes completely. They say you should check where your layout starts to break and create media queries only when necessary. Others will check for different device sizes, as you're doing now. But then you'll have a media query for 320px, another for 480px, and so on... You may go crazy with that, and maybe it's not even necessary depending on your layout!</p> <p>So, for now I'm trying to do both. I tend to ignore device sizes at first and will create some media queries only when necessary (when layout breaks), until it looks good for sizes like 960px and bigger, and also for smaller screen sizes, like 320px (the smallest device size I care about).</p>
    singulars
    1. This table or related slice is empty.
    1. POMedia query to target most of smartphone
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USrafaelbiten
    1. USrafaelbiten
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMedia query to target most of smartphone
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI really like the idea that I should concentrate on the content of my page rather than the size of the devices that will read my content. And this solve the problem even for future devices!
      singulars
      1. PO
      1. USNLemay
    2. COYep. Another thing that I would add, now that I read Mario's answer is that I also read things about the Mobile First idea but that doesn't make much sense to me. Maybe I just have to read more about it and try it myself but, when it comes to design, I think it's easier to adapt when making things smaller (like hiding not so important things); the bigger audience normally comes from desktops (and bigger res phones in the future); so why would I start with mobile? This is personal opinion, but the Mobile First idea looks "awkward" to me and I'm opened to change this with some good arguments =)
      singulars
      1. PO
      1. USrafaelbiten
 

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