Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not entirely sure what you mean by "best practice", but one thing I'd improve are the semantics. You could (should?) use <code>&lt;fieldset&gt;</code>'s instead of a, rather meaningless, <code>&lt;div&gt;</code>.</p> <p>And you don't need to use two <code>&lt;div&gt;</code>'s around the <code>textarea</code>, or even multiple background images on a single <code>&lt;div&gt;</code> (which is a CSS3 property, and not widely-supported).</p> <p>Instead, you should wrap the <code>&lt;textarea&gt;</code> in a <code>&lt;label&gt;</code> element, and nest your background-images as I've described below:</p> <p>Try this:</p> <pre><code>&lt;fieldset class="expandableInput"&gt; &lt;label&gt; Semantic text: &lt;textarea&gt;&lt;/textarea&gt; &lt;/label&gt; &lt;/fieldset&gt; </code></pre> <p><em>Bonus: wrapping form elements in <code>&lt;label&gt;</code>'s like this, affords a larger click area, for the user to gain focus on the form element at hand. Just be wary of <code>&lt;select&gt;</code>'s, which doesn't play nice (even though it's valid HTML)</em></p> <p>The CSS would be something like:</p> <pre><code>.expandableInput {background: url(/path/to/first/img);} .expandableInput label {display: block; background: url(/path/to/second/img);} .expandableInput textarea {display: block; margin-top: 3px; background: url(/path/to/third/img);} </code></pre> <p>Also; For consistent looks on form elements, in every browser &amp; platform, I can highly recommend Nathan Smith's <a href="http://formalize.me/" rel="nofollow">Formalize CSS</a> (it requires JS for HTML5 support in older browsers).</p>
    singulars
    1. This table or related slice is empty.
    1. POForm styling best practices
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UScabgfx
    1. UScabgfx
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POForm styling best practices
      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. COThanks CabGFX, that really helped. Formalize looks really neat, and I'll give it a try later. As for what I was trying to do, I needed three background images (top, middle repeat, and bottom). I'll look into the Fieldset tag more, and see how I can keep the form more semantic. I don't think you'd want to wrap all of your text areas with fieldsets, though I could be wrong. In any case, this has helped. Thanks!
      singulars
      1. PO
      1. USAkaishen
    2. COGlad it helped - enough to accept the answer? You're right with regards to `<fieldset>`, it is meant to logically group one or more fields in your form, preferably with a `<legend>` to denote the context of the fields. I'll edit my answer with more details for achieving your three background images.
      singulars
      1. PO
      1. UScabgfx
    3. COYes, it warrants an accepted answer. I apologize for my delay; I forgot as I'm still rather new here. ;) Using the label is an awesome idea! Thank you, again, for your help.
      singulars
      1. PO
      1. USAkaishen
 

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