Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Let's start with an explanation of what jQuery UI downloads are: They're a full bundle of development and production files. Keep in mind that jQuery UI is downloaded over 11,000 times per day (and that's just the download builder usage). The ways in which these downloads are used can vary greatly among users. The contents of these downloads are intended to serve the largest number of users. It's important to note that the development bundle is almost an exact copy of the source repository.</p> <p><strong>source, demos, themes, tests</strong></p> <ul> <li><code>MANIFEST</code>: This is a file containing a list of every other file in the zip, along with checksums. Very few users will care about the manifest, but for those who do care, it provides critical information.</li> <li><code>README.md</code>: (note that you listed <code>README.txt</code>): This is the README for the jquery-ui git repository. It's an exact copy of what you will see if you view the project on GitHub.</li> <li><code>*.json</code>: These are plugin manifest files for the <a href="http://plugins.jquery.com/" rel="noreferrer">jQuery Plugin Registry</a>. These files are never stored in the master branch (or any other branch), but are always included in tags. Because they provide useful information, they're included in the downloads. You can <a href="http://plugins.jquery.com/docs/package-manifest/" rel="noreferrer">read more about the manifest file structure</a>.</li> <li><code>package.json</code>: package.json is a standard file for use with <a href="http://npmjs.org/" rel="noreferrer">npm</a>/<a href="http://nodejs.org/" rel="noreferrer">node</a>. All jQuery projects rely on node to do linting, testing, builds, releases, etc. This is completely separate from the other JSON files which are for the jQuery Plugin Registry. They have very similar structures, because the plugin manifest files were designed based on npm.</li> <li><code>external</code>: This directory contains third party scripts which are used in demos and tests.</li> <li><code>jquery-1.9.1.js</code>: This is the latest stable version of jQuery that jQuery UI was tested against. We never include minified jQuery versions in the jQuery UI repository since they're horrible for debugging.</li> <li><code>MIT-LICENSE.txt</code>: The license which defines the terms under which you can use the files in the download.</li> <li><code>AUTHORS.txt</code>: A list of contributors to the jquery-ui repository. This does not include contributors to other parts of the jQuery UI project, such as work on any of our various sites or documentation.</li> <li><code>demos</code>: A directory of demos for the selected components (in this case all components). The demos actually originate in the jquery-ui repo and are copied to jqueryui.com during releases.</li> <li><code>Gruntfile.js</code>: We use <a href="http://gruntjs.com/" rel="noreferrer">Grunt</a> for linting, testing, and building. Grunt is a JavaScript task runner for node. Building jQuery UI means minification and concatenation.</li> <li><code>tests</code>: A directory of tests for the selected components (in this case all components).</li> <li><code>ui</code>: A copy of the source files, with @VERSION replaced with the release's version number. The <code>jquery-ui.js</code> file is generated during the build by concatenating all of the source files together. The <code>minified</code> directory is generated during the build by minifying the individual files. And of coure <code>jquery-ui.min.js</code> is generated by both concatenating and minifying the source files.</li> <li><code>themes</code>: A copy of the source files, with @VERSION replaced with the release's version number. This undergoes the same process as the <code>ui</code> directory regarding concatenation and minification. The individual component files are theme-independent. So <code>jquery.ui.accordion.css</code> will work with any theme. These are the required CSS files for use with the JS files. You can build any theme you want, but if you don't use the functional CSS for the component, then nothing is guaranteed to work. Full themes (what pretty much all users actually use), contain all of the functional CSS plus the theme CSS in a single file.</li> </ul> <p><strong>themes</strong></p> <p>Themes are generated by <a href="http://jqueryui.com/themeroller/" rel="noreferrer">ThemeRoller</a>. They do not live in any repository and as such do not contain artifacts of any repository. This is why there is no README.</p> <ul> <li><code>MANIFEST</code>: Same as above, the manifest contains checksums for the files in the download.</li> <li><code>AUTHORS.txt</code>: A copy of <code>AUTHORS.txt</code> from jquery-ui. This should exactly match the source download. While this isn't a list of people who have contributed to themes, we view this as part of the code and include the same list of authors.</li> <li><code>package.json</code>: A copy of <code>package.json</code> from jquery-ui. This file does seem a bit strange, since it's not coming from a repository. We should probably remove this.</li> <li><code>themes</code>: A directory of generated themes. These do not contain the source variables/tokens. The base theme is not a generated theme and therefore is not included. You'll notice that generated themes also have a different directory structure. Each theme contains three files: <code>jquery.ui.theme.css</code> is just the theme CSS; this is what can be used with the functional CSS provided in the base theme. <code>jquery-ui.css</code> is a full theme; it includes the theme CSS plus the functional CSS. <code>jquery-ui.min.css</code> is a minified copy of <code>jquery-ui.css</code>.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POjQuery UI downloads - what are each of the directories in the archive holding?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USScott González
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POjQuery UI downloads - what are each of the directories in the archive holding?
      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. VTAcceptedByOriginator
    1. COThanks for responding Scott, but 2 things come to mind. Firstly, just because the download is used in lots of ways does not mean that you should skimp on the documentation, and this answer could (and probably should) be copy and pasted into the README and it would improve things 100%. Secondly, where you say about Themes that "This is why there is no README"… no, if it's a download should have a README.
      singulars
      1. PO
      1. USiain
    2. COScott, regarding images, will all the images in a theme from the Themes download, say `black-tie/images`, satisfy the `black-tie/jquery-ui.css` requirements, or do the `themes/base/images` from the source download need to be added too? Or another way of putting it, if the `jquery-ui.css` and `images` dir are used from a theme in the Themes download, is that enough, or is there something else to be added/referenced?
      singulars
      1. PO
      1. USiain
    3. COEach theme is fully self contained. You never need to mix anything.
      singulars
      1. PO
      1. USScott González
 

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