Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>My answer applies to Rails 3.1rc4, I don't know whether it functions the same with other versions.</p> <p>You can actually put all require statements in app/assets/javascripts/application.js whether or not the .js files are in app/assets/javascripts/ or vendor/assets/javascripts/</p> <p>Like so:</p> <pre><code>// this is in app/assets/javascripts/application.js //= require modernizr-2.0 //= require jquery //= require jquery_ujs //= require jqueryui-1.8.12 //= require jquery.easing-1.3 //= require jquery.noisy //= require jquery.jslide-1.0 //= require respond //= require smoke //= require_tree </code></pre> <p>I included require_tree here because I have other javascript files for my individual controllers (pages.js.coffee, users.js.coffee) and a general one for site-wide stuff (site.js.coffee)</p> <p>Meanwhile here's the file structure.</p> <pre><code>app/ ├── assets │ ├── javascripts │ │ ├── application.js │ │ ├── pages.js.coffee │ │ ├── users.js.coffee │ │ └── site.js.coffee │ └── stylesheets └── plugins vendor/ ├── assets │ ├── javascripts │ │ ├── jquery.easing-1.3.js │ │ ├── jquery.jslide-1.0.js │ │ ├── jquery.noisy.js │ │ ├── jqueryui-1.8.12.js │ │ ├── modernizr-2.0.js │ │ ├── respond.js │ │ └── smoke.js │ └── stylesheets └── plugins </code></pre> <p>This allows me to control the load order of vendor libraries (which matters a lot, usually) and not worry about my internal javascript, where order generally matters less.</p> <p>More importantly, I control all require statements within one often used file, I find that both safer and cleaner.</p>
    singulars
    1. This table or related slice is empty.
    1. PORails 3.1 asset pipeline and manually ordered Javascript requires
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USOlivier Lacan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. CO+1 for this way of handling assets dependencies. This is in the Rails' way as per the guides http://guides.rubyonrails.org/asset_pipeline.html#asset-organization. Also remember to restart your Rails server after moving files around!
      singulars
      1. PO
      1. USbrutuscat
    2. COBut this loads too much JS at once. Much better to `//= require` your dependencies only where they're actually needed. In general I think the Rails 3.1 way of organizing JS is not fine-grained enough for well-designed applications.
      singulars
      1. PO
      1. USMarnen Laibow-Koser
    3. CO@MarnenLaibow-Koser The Rails idea is that loading a big bunch of js/css at a time is good, because then the browser can cache that and then for any subsequent requests no assets need to be fetched from the server. So the initial load is slower, but subsequent requests are fast when every page do not have it's own css styles and js files. This also promotes writing sane and reusable css. However, you can of course tune the asset pipeline to be as finely granulated as you wish.
      singulars
      1. PO
      1. USTimo
 

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