locomotivecms 3.2.0.rc1 → 3.2.0.rc2

data/vendor/assets/components/locomotive_sources/select2/docs/_includes/options/compatibility/introduction.html

@@ -1,18 +0,0 @@
-<section>
-  <p>
-    Select2 offers limited backwards compatibility with the previously 3.5.x
-    release line, allowing people more efficiently transfer across releases
-    and get the latest features. For many of the larger changes, such as the
-    change in how custom data adapters work, compatibility modules were
-    created that will be used to assist in the upgrade process. It is not
-    recommended to rely on these compatibility modules, as they will not
-    always exist, but they make upgrading easier for major changes.
-  </p>
-
-  <p>
-    <strong>The compatibility modules are only included in the
-    <a href="index.html#builds-full" class="alert-link">full builds</a> of
-    Select2</strong>. These files end in <code>.full.js</code>, and the
-    compatibility modules are prefixed with <code>select2/compat</code>.
-  </p>
-</section>

data/vendor/assets/components/locomotive_sources/select2/docs/_includes/options/compatibility/matcher.html

@@ -1,50 +0,0 @@
-<section>
-  <h2 id="compat-matcher">
-    Simplified function for matching data objects
-  </h2>
-
-  <p class="alert alert-info">
-    <a href="announcements-4.0.html#new-matcher" class="alert-link">Added in Select2 4.0.0.</a>
-    This method was added to make upgrading easier from earlier versions of
-    Select2.
-  </p>
-
-  <p>
-    During the <a href="announcements-4.0.html">Select2 4.0.0 release</a>, the
-    <code>matcher</code> function was changed to allow for more complex
-    matching of nested objects.
-  </p>
-
-  <div class="row">
-    <div class="col-sm-6">
-      <dl class="dl-horizontal">
-        <dt>Key</dt>
-        <dd>
-          <code>matcher</code>
-        </dd>
-
-        <dt>Value</dt>
-        <dd>
-          A function taking a search <code>term</code> and the data object
-          <code>text</code>.
-        </dd>
-      </dl>
-    </div>
-
-    <div class="col-sm-6">
-      <dl class="dl-horizontal">
-        <dt>Adapter</dt>
-        <dd>
-          <code title="select2/compat/matcher">oldMatcher</code>
-        </dd>
-      </dl>
-    </div>
-  </div>
-
-  <p>
-    The <a href="examples.html#matcher">custom matcher example</a> provides a
-    guide for how to use this in your own application. For those upgrading
-    from older versions of Select2, you just need to wrap your old
-    <code>matcher</code> with this function to maintain compatibility.
-  </p>
-</section>

data/vendor/assets/components/locomotive_sources/select2/docs/_includes/options/compatibility/query-function.html

@@ -1,50 +0,0 @@
-<section>
-  <h2 id="query">
-    Querying old data with <code>query</code>
-  </h2>
-
-  <p class="alert alert-warning">
-    <a href="announcements-4.0.html#query-to-data-adapter" class="alert-link">Deprecated in Select2 4.0.</a>
-    This has been replaced by another option and is only available in the
-    <a href="index.html#builds-full" class="alert-link">full builds</a> of
-    Select2.
-  </p>
-
-  <p>
-    In the past, Select2 supported an option called <code>query</code> that
-    allowed for a custom data source to be used. This option has been replaced
-    by the <code>query</code> method on the
-    <a href="#dataAdapter">data adapter</a> and takes a very similar set of
-    parameters.
-  </p>
-
-  <div class="row">
-    <div class="col-sm-6">
-      <dl class="dl-horizontal">
-        <dt>Key</dt>
-        <dd>
-          <code>query</code>
-        </dd>
-
-        <dt>Value</dt>
-        <dd>
-          A function taking <code>params</code> (including a <code>callback</code>)
-        </dd>
-      </dl>
-    </div>
-
-    <div class="col-sm-6">
-      <dl class="dl-horizontal">
-        <dt>Adapter</dt>
-        <dd>
-          <code title="select2/data/base">DataAdapter</code>
-        </dd>
-
-        <dt>Decorator</dt>
-        <dd>
-          <code title="select2/compat/query">Query</code>
-        </dd>
-      </dl>
-    </div>
-  </div>
-</section>

data/vendor/assets/components/locomotive_sources/select2/docs/_includes/options/compatibility/text-input.html

@@ -1,32 +0,0 @@
-<section>
-  <h2 id="input-fallback">
-    Compatibility with <code>&lt;input type="text" /&gt;</code>
-  </h2>
-
-  <p class="alert alert-warning">
-    <a href="announcements-4.0.html#hidden-input" class="alert-link">Deprecated in Select2 4.0.</a>
-    It is now encouraged to use the <code>&lt;select&gt;</code> tag instead.
-  </p>
-
-  <p>
-    In past versions of Select2, a <code>&lt;select&gt;</code> element could
-    only be used with a limited subset of options. An
-    <code>&lt;input type="hidden" /&gt;</code> was required instead, which did
-    not allow for a graceful fallback for users who did not have JavaScript
-    enabled. Select2 now supports the <code>&lt;select&gt;</code> element for
-    all options, so it is no longer required to use <code>&lt;input /&gt;</code>
-    elements with Select2.
-  </p>
-
-  <dl class="dl-horizontal">
-    <dt>Adapter</dt>
-    <dd>
-      <code title="select2/data/base">DataAdapter</code>
-    </dd>
-
-    <dt>Decorator</dt>
-    <dd>
-      <code title="select2/compat/inputData">InputData</code>
-    </dd>
-  </dl>
-</section>

data/vendor/assets/components/locomotive_sources/select2/docs/_includes/options/core.html

@@ -1,9 +0,0 @@
-<section>
-  <h1>
-    Core options
-  </h1>
-
-  {% include options/core/options.html %}
-  {% include options/core/data-attributes.html %}
-  {% include options/core/amd-support.html %}
-</section>

data/vendor/assets/components/locomotive_sources/select2/docs/_includes/options/core/amd-support.html

@@ -1,38 +0,0 @@
-<section>
-  <h2 id="amd">
-    Can I use Select2 with my AMD or CommonJS loader?
-  </h2>
-
-  <p>
-    Yes, Select2 should work with most AMD or CommonJS loaders without any issues.
-  </p>
-
-  <h3>
-    How do I tell Select2 where to look for modules?
-  </h3>
-
-  <p>
-    For most AMD and CommonJS setups, the location of the data files used by Select2 will be automatically determined and handled without you needing to do anything.
-  </p>
-
-  <p>
-    If you are using Select2 in a build environment where preexisting module names are changed during a build step, Select2 may not be able to find optional dependencies or language files. You can manually set the prefixes to use for these files using the <code>amdBase</code> and <code>amdLanugageBase</code> options.
-  </p>
-
-<pre class="prettyprint">
-$.fn.select2.defaults.set('amdBase', 'select2/');
-$.fn.select2.defaults.set('amdLanguageBase', 'select2/i18n/');
-</pre>
-
-  <h3>
-    Select2 is being placed before jQuery in my JavaScript file
-  </h3>
-
-  <p>
-    Due to a bug in older versions of the r.js build tool, Select2 was sometimes placed before jQuery in then compiled build file. Because of this, Select2 will trigger an error because it won't be able to find or load jQuery.
-  </p>
-
-  <p>
-    You can fix this issue by upgrading to a newer version of the r.js build tool.
-  </p>
-</section>

data/vendor/assets/components/locomotive_sources/select2/docs/_includes/options/core/data-attributes.html

@@ -1,72 +0,0 @@
-<section>
-  <h2 id="data-attributes">
-    Can I declare my configuration within the HTML?
-  </h2>
-
-  <p>
-    It is recommended that you declare your configuration options for Select2
-    when initializing Select2. You can also define your configuration options
-    by using the HTML5 <code>data-*</code> attributes, which will override
-    any options set when initializing Select2 and any defaults.
-  </p>
-
-  <h3>
-    How should <code>camelCase</code> options be written?
-  </h3>
-
-  <p>
-    This means that if you declare your <code>&lt;select&gt;</code> tag as...
-  </p>
-
-<pre class="prettyprint">
-&lt;select data-tags="true" data-placeholder="Select an option" data-allow-clear="true"&gt;&lt;/select&gt;
-</pre>
-
-  <p>
-    Will be interpreted the same as initializing Select2 as...
-  </p>
-
-<pre class="prettyprint linenums">
-$("select").select2({
-  tags: "true",
-  placeholder: "Select an option",
-  allowClear: true
-});
-</pre>
-
-  <h3>
-    Are options with nested configurations supported?
-  </h3>
-
-  <p>
-    You can also define nested configurations, which are typically needed for
-    options such as AJAX. Each level of nesting should be separated by two
-    dashes (<code>--</code>) instead of one. Due to
-    <a href="https://github.com/jquery/jquery/issues/2070">a jQuery bug</a>,
-    nested options using <code>data-*</code> attributes
-    <a href="https://github.com/select2/select2/issues/2969">do not work in jQuery 1.x</a>.
-  </p>
-
-<pre class="prettyprint">
-&lt;select data-ajax--url="http://example.org/api/test" data-ajax--cache="true"&gt;&lt;/select&gt;
-</pre>
-
-  <p>
-    Which will be interpreted the same as initializing Select2 with...
-  </p>
-
-<pre class="prettyprint linenums">
-$("select").select2({
-  ajax: {
-    url: "http://example.org/api/test",
-    cache: "true"
-  }
-});
-</pre>
-
-  <p>
-    The value of the option is subject to jQuery's
-    <a href="https://api.jquery.com/data/#data-html5">parsing rules</a> for
-    HTML5 data attributes.
-  </p>
-</section>

data/vendor/assets/components/locomotive_sources/select2/docs/_includes/options/core/options.html

@@ -1,58 +0,0 @@
-<section>
-  <h2 id="options">
-    How should Select2 be initialized?
-  </h2>
-
-  <h3 id="setting-default-options">
-    Can default options be set for all dropdowns?
-  </h3>
-
-  <p>
-    In some cases, you need to set the default options for all instances of
-    Select2 in your web application. This is especially useful when you are
-    migrating from past versions of Select2, or you are using non-standard
-    options <a href="#amd">like custom AMD builds</a>. Select2 exposes the
-    default options through <code>$.fn.select2.defaults</code>, which allows
-    you to set them globally.
-  </p>
-
-  <p>
-    When setting options globally, any past defaults that have been set will
-    be overriden. Default options are only used when an option is requested
-    that has not been set during initialization.
-  </p>
-
-  <p>
-    <strong>You can set default options</strong> by calling
-    <code>$.fn.select2.defaults.set("key", "value")</code>.
-  </p>
-
-<pre class="prettyprint">
-$.fn.select2.defaults.set("theme", "classic");
-</pre>
-
-  <h3>
-    How can I set a default value for a nested option?
-  </h3>
-
-  <p>
-    The key that is
-    set should take the same format as keys set using
-    <a href="#data-attributes">HTML <code>data-*</code> attributes</a> which
-    means that two dashes (<code>--</code>) will be replaced by a level of
-    nesting, and a single dash (<code>-</code>) will convert it to a camelCase
-    string.
-  </p>
-
-  <h3>
-    How can I reset all of the global default options?
-  </h3>
-
-  <p>
-    You can reset the default options by calling
-  </p>
-
-<pre class="prettyprint">
-$.fn.select2.defaults.reset();
-</pre>
-</section>

data/vendor/assets/components/locomotive_sources/select2/docs/_includes/options/data.html

@@ -1,9 +0,0 @@
-<section>
-  <h1>
-    Data adapters
-  </h1>
-
-  {% include options/data/select.html %}
-  {% include options/data/array.html %}
-  {% include options/data/ajax.html %}
-</section>

data/vendor/assets/components/locomotive_sources/select2/docs/_includes/options/data/ajax.html

@@ -1,109 +0,0 @@
-<section>
-  <h2 id="ajax">
-    Can Select2 be connected to a remote data source?
-  </h2>
-
-  <p>
-    Select2 supports connecting to a remote data source using the <code>ajax</code> option.
-  </p>
-
-  <h3>
-    How can I set the initially selected options when using AJAX?
-  </h3>
-
-  <p>
-    You can refer to the following Stack Overflow answer if you want to set the initial value for AJAX requests: <a href="http://stackoverflow.com/q/30316586/359284#30328989">Select2 4.0.0 initial value with AJAX</a>
-  </p>
-
-  <h3>
-    What should the results returned to Select2 look like?
-  </h3>
-
-  {% include options/not-written.html %}
-
-  <h3>
-    Is there a way to modify the response before passing it back to Select2?
-  </h3>
-
-  <p>
-    You can use the <code>ajax.processResults</code> option to modify the data returned from the server before passing it to Select2.
-  </p>
-
-<pre class="prettyprint">
-$('select').select2({
-  ajax: {
-    url: '/example/api',
-    processResults: function (data) {
-      return {
-        results: data.items
-      };
-    }
-  }
-});
-</pre>
-
-  <h3>
-    A request is being triggered on every key stroke, can I delay this?
-  </h3>
-
-  <p>
-    By default, Select2 will trigger a new AJAX request whenever the user changes their search term. You can set a time limit for debouncing requests using the <code>ajax.delay</code> option.
-  </p>
-
-<pre class="prettyprint">
-$('select').select2({
-  ajax: {
-    url: '/example/api',
-    delay: 250
-  }
-});
-</pre>
-
-  <p>
-    This will tell Select2 to wait 250 milliseconds before sending the request out to your API.
-  </p>
-
-  <h3>
-    I want to add more query parameters to the request, where can this be done?
-  </h3>
-
-  <p>
-    By default, Select2 will send the query term as well as the pagination data as query parameters in requests. You can override the data that is sent to your API, or change any of the query paramters, by overriding the <code>ajax.data</codE> option.
-  </p>
-
-<pre class="prettyprint">
-$('select').select2({
-  ajax: {
-    data: function (params) {
-      var query = {
-        search: params.term,
-        page: params.page
-      }
-
-      // Query paramters will be ?search=[term]&page=[page]
-      return query;
-    }
-  }
-});
-</pre>
-
-  <h3>
-    Can an AJAX plugin other than <code>jQuery.ajax</code> be used?
-  </h3>
-
-  <p>
-    Select2 uses the transport method defined in <code>ajax.transport</code> to send requests to your API. By default, this transport method is <code>jQuery.ajax</code> but this can be changed.
-  </p>
-
-<pre class="prettyprint">
-$('select').select2({
-  ajax: {
-    transport: function (params, success, failure) {
-      var request = new AjaxRequest(params.url, params);
-      request.on('success', success);
-      request.on('failure', failure);
-    }
-  }
-});
-</pre>
-</section>