RubyGems - RubyApp - Versions diffs - 0.6.59 → 0.6.60 - Mend

RubyApp 0.6.59 → 0.6.60

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (870) hide show

data/lib/ruby_app/resources/elements/mobile/document/jquery.mobile-1.1.0/demos/docs/api/globalconfig.html ADDED

@@ -0,0 +1,181 @@
+<!DOCTYPE html>
+<html>
+	<head>
+	<meta charset="utf-8">
+	<meta name="viewport" content="width=device-width, initial-scale=1">
+	<title>jQuery Mobile Docs - Configuring default settings</title>
+	<link rel="stylesheet"  href="../../css/themes/default/jquery.mobile-1.1.0.css" />
+	<link rel="stylesheet" href="../_assets/css/jqm-docs.css"/>
+	<script src="../../js/jquery.js"></script>
+	<script src="../../docs/_assets/js/jqm-docs.js"></script>
+	<script src="../../js/jquery.mobile-1.1.0.js"></script>
+</head>
+<body>
+<div data-role="page" class="type-interior">
+	<div data-role="header" data-theme="f">
+		<h1>Configuring Defaults</h1>
+		<a href="../../" data-icon="home" data-iconpos="notext" data-direction="reverse">Home</a>
+		<a href="../nav.html" data-icon="search" data-iconpos="notext" data-rel="dialog" data-transition="fade">Search</a>
+	</div><!-- /header -->
+	<div data-role="content" data-theme="c">
+		<div class="content-primary">
+			<h2>Working with jQuery Mobile's Auto-initialization</h2>
+			<p>Unlike other jQuery projects, such as jQuery and jQuery UI, jQuery Mobile automatically applies many markup enhancements as soon as it loads (long before the <code>document.ready</code> event fires). These enhancements are applied based on jQuery Mobile's default settings, which are designed to work with common scenarios. If changes to the settings are needed, they are easy to configure.</p>
+			<h3>The mobileinit event</h3>
+			<p>When jQuery Mobile starts, it triggers a <code>mobileinit</code> event on the <code>document</code> object. To override default settings, bind to <code>mobileinit</code>.</p>
+			<pre>
+				<code>
+$(document).bind("mobileinit", function(){
+  //apply overrides here
+});
+				</code>
+			</pre>
+			<p>Because the <code>mobileinit</code> event is triggered immediately, you'll need to bind your event handler before jQuery Mobile is loaded. Link to your JavaScript files in the following order:</p>
+			<pre>
+				<code>
+&lt;script src=&quot;jquery.js&quot;&gt;&lt;/script&gt;
+<strong>&lt;script src=&quot;custom-scripting.js&quot;&gt;&lt;/script&gt;</strong>
+&lt;script src=&quot;jquery-mobile.js&quot;&gt;&lt;/script&gt;
+				</code>
+			</pre>
+			<p>You can override default settings by extending the <code>$.mobile</code> object using jQuery's <code>$.extend</code> method.</p>
+			<pre>
+				<code>
+$(document).bind("mobileinit", function(){
+  $.extend(  $.mobile , {
+    <strong>foo: bar</strong>
+  });
+});
+				</code>
+			</pre>
+			<p>Alternatively, you can set them using object property notation.</p>
+			<pre>
+				<code>
+$(document).bind("mobileinit", function(){
+  <strong>$.mobile.foo = bar;</strong>
+});
+				</code>
+			</pre>
+		<p>To explore the effects of global configuration options, see the <a href="../config/index.html">config test pages</a>.</p>
+		<h2>Configurable options</h2>
+		<p>The following defaults are configurable via the <code>$.mobile</code> object:</p>
+<dl>
+	<dt><code>activeBtnClass</code> <em>string</em>, default: "ui-btn-active"</dt>
+	<dd>The CSS class used for "active" button state.</dd>
+	<dt><code>activePageClass</code> <em>string</em>, default: "ui-page-active"</dt>
+	<dd>The CSS class used for the page currently in view or in a transition.</dd>
+	<dt><code>ajaxEnabled</code> <em>boolean</em>, default: true</dt>
+	<dd>jQuery Mobile will automatically handle link clicks and form submissions through Ajax, when possible. If false, URL hash listening will be disabled as well, and URLs will load as ordinary HTTP requests.</dd>
+	<dt><code>allowCrossDomainPages</code> <em>boolean</em>, default: false</dt>
+	<dd>When jQuery Mobile attempts to load an external page, the request runs through <code>$.mobile.loadPage()</code>. This will only allow cross-domain requests if <code>$.mobile.allowCrossDomainPages</code> is set to true. Because the jQuery Mobile framework tracks what page is being viewed within the browser's location hash, it is possible for a cross-site scripting (XSS) attack to occur if the XSS code in question can manipulate the hash and set it to a cross-domain URL of its choice. This is the main reason that the default setting for $.mobile.allowCrossDomainPages is set to false. In PhoneGap apps that must "phone home" by loading assets off a remote server, both the <code>$.support.cors</code> AND <code>$.mobile.allowCrossDomainPages</code> must be set to true.</dd>
+	<dt><code>autoInitializePage</code> <em>boolean</em>, default: true</dt>
+	<dd>When the DOM is ready, the framework should automatically call <code>$.mobile.initializePage</code>. If false, the page will not initialize and will be visually hidden until <code>$.mobile.initializePage</code> is manually called.</dd>
+	<dt><code>buttonMarkup.hoverDelay</code> <em>integer</em>, default: 200</dt>
+	<dd>Set the delay for touch devices to add the hover and down classes on touch interactions for buttons throughout the framework. Reducing the delay here results in a more responsive feeling ui, but will often result in the downstate being applied during page scrolling.</dd>
+	<dt><code>defaultDialogTransition</code> <em>string</em>, default: 'pop'</dt>
+	<dd>Set the default transition for dialog changes that use Ajax. Set to 'none' for no transitions.</dd>
+	<dt><code>defaultPageTransition</code> <em>string</em>, default: 'fade'</dt>
+	<dd>Set the default transition for page changes that use Ajax. Note: default changed from 'slide' to 'fade' in 1.1. Set to 'none' for no transitions.</dd>
+	<dt><code>gradeA</code> <em>function that returns a boolean</em>, default: a function returning the value of $.support.mediaquery</dt>
+	<dd>Any support conditions that must be met in order to proceed.</dd>
+	<dt><code>hashListeningEnabled</code> <em>boolean</em>, default: true</dt>
+	<dd>jQuery Mobile will automatically listen and handle changes to the location.hash. Disabling this will prevent jQuery Mobile from handling hash changes, which allows you to handle them yourself or use simple deep-links within a document that scroll to a particular ID.</dd>
+	<dt><code>ignoreContentEnabled</code> <em>boolean</em>, default: false</dt>
+	<dd><em>Warning:</em> Setting this property to true will cause performance degradation on enhancement. Once set, all automatic enhancements made by the framework to each enhanceable element of the user's markup will first check for a <code>data-enhance=false</code> parent node. If one is found the markup will be ignored. This setting and the accompanying data attribute provide a mechanism through which users can prevent enhancement over large sections of markup.</dd>
+	<dt><code>linkBindingEnabled</code> <em>boolean</em>, default: true</dt>
+	<dd>jQuery Mobile will automatically bind the clicks on anchor tags in your document. Setting this options to false will prevent all anchor click handling <em>including</em> the addition of active button state and alternate link bluring. This should only be used when attempting to delegate the click management to another library or custom code.</dd>
+	<dt><code>loadingMessage</code> <em>string</em>, default: "loading"</dt>
+	<dd>Set the text that appears when a page is loading. If set to false, the message will not appear at all.</dd>
+	<dt><code>loadingMessageTextVisible</code> <em>boolean</em>, default: false</dt>
+	<dd>Whether the text should be visible when a loading message is shown. The text is always visible for loading errors.</dd>
+	<dt><code>loadingMessageTheme</code> <em>string</em>, default: "a"</dt>
+	<dd>The theme that the loading message box uses when text is visible.</dd>
+	<dt><code>minScrollBack</code> <em>string</em>, default: 250</dt>
+	<dd>Minimum scroll distance that will be remembered when returning to a page.</dd>
+	<dt><code>ns</code> <em>string</em>, default: ""</dt>
+	<dd>The namespace used in data- attributes (e.g., data-role). Can be set to any string, including a blank string which is the default. When using, it's clearest if you include a trailing dash, such as "mynamespace-" which maps to <code>data-mynamespace-foo="..."</code>.
+		<p>If you use data- namespacing, you will need to update/override one selector in the theme CSS. The following data selectors should incorporate the namespace you're using:
+		<pre><code>
+.ui-mobile [data-<strong>mynamespace-</strong>role=page], .ui-mobile [data-<strong>mynamespace-</strong>role=dialog], .ui-page { ...
+		</code></pre>
+		</p>
+	</dd>
+	<dt><code>pageLoadErrorMessage</code> <em>string</em>, default: "Error Loading Page"</dt>
+	<dd>Set the text that appears when a page fails to load through Ajax.</dd>
+	<dt><code>pageLoadErrorMessageTheme</code> <em>string</em>, default: "e"</dt>
+	<dd>Set the theme that the error message box uses.</dd>
+	<dt><code>pushStateEnabled</code> <em>boolean</em>, default: true</dt>
+	<dd>Enhancement to use <code>history.replaceState</code> in supported browsers, to convert the hash-based Ajax URL into the full document path. Note that we <a href="../pages/page-navmodel.html">recommend</a> disabling this feature if Ajax is disabled or if extensive use of external links are used.</dd>
+	<dt><code>subPageUrlKey</code> <em>string</em>, default: "ui-page"</dt>
+	<dd>The url parameter used for referencing widget-generated sub-pages (such as those generated by nested listviews). Translates to <em>example.html<strong>&ui-page=</strong>subpageIdentifier</em>. The hash segment before &ui-page= is used by the framework for making an Ajax request to the URL where the sub-page exists.</dd>
+	<dt><code>touchOverflowEnabled</code> <em>boolean</em>, default: false</dt>
+	<dd>Enable smoother page transitions and true fixed toolbars in devices that support both the <code>overflow:</code> and <code>overflow-scrolling: touch; </code> CSS properties. <strong>Note: Deprecated for 1.1.0.</strong></dd>
+</dl>
+	</div><!--/content-secondary -->
+	<div class="content-secondary">
+		<div data-role="collapsible" data-collapsed="true" data-theme="b" data-content-theme="d">
+				<h3>More in this section</h3>
+				<ul data-role="listview"  data-theme="c" data-dividertheme="d">
+					<li data-role="list-divider">API</li>
+					<li data-theme="a"><a href="../../docs/api/globalconfig.html">Configuring defaults</a></li>
+					<li><a href="../../docs/api/events.html">Events</a></li>
+					<li><a href="../../docs/api/methods.html">Methods &amp; Utilities</a></li>
+					<li><a href="../../docs/api/data-attributes.html">Data attribute reference</a></li>
+					<li><a href="../../docs/api/themes.html">Theme framework</a></li>
+				</ul>
+		</div>
+	</div>
+</div><!-- /content -->
+<div data-role="footer" class="footer-docs" data-theme="c">
+		<p>&copy; 2011-12 The jQuery Foundation</p>
+</div>
+</div><!-- /page -->
+</body>
+</html>

data/lib/ruby_app/resources/elements/mobile/document/jquery.mobile-1.1.0/demos/docs/api/index.html ADDED

@@ -0,0 +1,40 @@
+<!DOCTYPE html>
+<html>
+<head>
+	<meta charset="utf-8">
+	<meta name="viewport" content="width=device-width, initial-scale=1">
+	<title>jQuery UI Mobile Framework - API</title>
+	<link rel="stylesheet"  href="../../css/themes/default/jquery.mobile-1.1.0.css" />
+	<link rel="stylesheet" href="../_assets/css/jqm-docs.css"/>
+	<script src="../../js/jquery.js"></script>
+	<script src="../../docs/_assets/js/jqm-docs.js"></script>
+	<script src="../../js/jquery.mobile-1.1.0.js"></script>
+</head>
+<body>
+<div data-role="page" class="type-index">
+<div data-role="header" data-theme="f">
+	<h1>API</h1>
+	<a href="../../" data-icon="home" data-iconpos="notext" data-direction="reverse">Home</a>
+		<a href="../nav.html" data-icon="search" data-iconpos="notext" data-rel="dialog" data-transition="fade">Search</a>
+</div>
+<div data-role="content">
+		<ul data-role="listview" data-inset="true" data-theme="c" data-dividertheme="f">
+			<li data-role="list-divider">API</li>
+			<li><a href="globalconfig.html">Configuring defaults</a></li>
+			<li><a href="events.html">Events</a></li>
+			<li><a href="methods.html">Methods &amp; Utilities</a></li>
+			<li><a href="data-attributes.html">Data attribute reference</a></li>
+			<li><a href="themes.html">Theme framework</a></li>
+		</ul>
+</div>
+</div>
+</body>
+</html>

data/lib/ruby_app/resources/elements/mobile/document/jquery.mobile-1.1.0/demos/docs/api/mediahelpers.html ADDED

@@ -0,0 +1,133 @@
+<!DOCTYPE html>
+<html>
+	<head>
+	<meta charset="utf-8">
+	<meta name="viewport" content="width=device-width, initial-scale=1">
+	<title>jQuery Mobile Docs - Responsive Layout Helpers</title>
+	<link rel="stylesheet"  href="../../css/themes/default/jquery.mobile-1.1.0.css" />
+	<link rel="stylesheet" href="../_assets/css/jqm-docs.css"/>
+	<script src="../../js/jquery.js"></script>
+	<script src="../../docs/_assets/js/jqm-docs.js"></script>
+	<script src="../../js/jquery.mobile-1.1.0.js"></script>
+</head>
+<body>
+<div data-role="page" class="type-interior">
+	<div data-role="header" data-theme="f">
+		<h1>Responsive Layout Helpers</h1>
+		<a href="../../" data-icon="home" data-iconpos="notext" data-direction="reverse">Home</a>
+		<a href="../nav.html" data-icon="search" data-iconpos="notext" data-rel="dialog" data-transition="fade">Search</a>
+	</div><!-- /header -->
+	<div data-role="content" data-theme="c">
+			<div class="content-primary">
+			<h2>Media Query Helper Classes</h2>
+<p class="ui-bar-e ui-body"><strong>Note: This feature was deprecated in beta, and removed in 1.0rc1. We recommend using CSS3 Media Queries instead.</strong> To support older versions of Internet Explorer, check out <a href="https://github.com/scottjehl/Respond">respond.js</a>, a fast &amp; lightweight polyfill for min/max-width CSS3 Media Queries.</p>
+			<p class="ui-bar-e ui-body">If you still need this feature, you can find the code here: <a href="https://raw.github.com/jquery/jquery-mobile/38d7ad8848f00b0921bf4ae723f3ad199eb851c1/js/jquery.mobile.media.classes.js">jquery.mobile.media.classes.js</a></p>
+			<p>jQuery Mobile adds classes to the <code>HTML</code> element that mimic browser orientation and common min/max-width CSS media queries. These classes are updated on load, resize and orientationchange, allowing you to key off these classes in your CSS, to create <a href="http://www.alistapart.com/articles/responsive-web-design/">responsive layouts</a> - even in browsers that don't support media queries! </p>
+			<h3>Orientation Classes </h3>
+			<p>The HTML element will always have a class of either <code>"portrait"</code> or <code>"landscape"</code>, depending on the orientation of the browser or device. You can utilize these in your CSS like this:</p>
+			<pre>
+			<code>
+.portrait {
+	/* portrait orientation changes go here! */
+}
+.landscape {
+	/* landscape orientation changes go here! */
+}
+			</code>
+			</pre>
+			<h3>Min/Max Width Breakpoint Classes</h3>
+			<p>By default, we create min and max breakpoint classes at the following widths: <code>320</code>,<code>480</code>,<code>768</code>,<code>1024</code>. These translate to classes that look like this: <code>"min-width-320px"</code>, <code>"max-width-480px"</code>, and are meant to be used as a replacement of (or in addition to) the media query equivalents they mimic.</p>
+<pre>
+			<code>
+.myelement {
+	float: none;
+}
+.min-width-480px .myelement {
+	float: left;
+}
+			</code>
+</pre>
+			<p>Many plugins in jQuery Mobile leverage these width breakpoints. For example, form elements float beside their labels when the browser is wider than 480 pixels. The CSS to support this behavior for form text inputs looks like this:</p>
+<pre>
+			<code>
+label.ui-input-text {
+	display: block;
+}
+.min-width-480px label.ui-input-text {
+	display: inline-block;
+}
+			</code>
+</pre>
+			<h3>Adding Width Breakpoints</h3>
+		<p>To utilize width breakpoints of your own, jQuery Mobile exposes the <code>$.mobile.addResolutionBreakpoints </code> function, which accepts either a single number or array of numbers that will be added to the min/max breakpoints whenever they apply.</p>
+<pre>
+			<code>
+//add a min/max class for 1200 pixel widths
+$.mobile.addResolutionBreakpoints(1200);
+//add min/max classes for 1200, and 1440 pixel widths
+$.mobile.addResolutionBreakpoints([1200, 1440]);
+			</code>
+</pre>
+<h3>Running Media Queries</h3>
+<p>jQuery Mobile provides a function that allows you to test whether a particular CSS Media Query applies. Simple call <code>$.mobile.media()</code> and pass a media type or query. If the browser supports that type or query, and it currently applies, the function will return true. If not, it'll return false.</p>
+<pre>
+			<code>
+//test for screen media type
+$.mobile.media("screen");
+//test  a min-width media query
+$.mobile.media("screen and (min-width: 480px)");
+//test for iOS retina display
+$.mobile.media("screen and (-webkit-min-device-pixel-ratio: 2)");
+			</code>
+</pre>
+	</div><!--/content-secondary -->
+	<div class="content-secondary">
+		<div data-role="collapsible" data-collapsed="true" data-theme="b" data-content-theme="d">
+				<h3>More in this section</h3>
+				<ul data-role="listview"  data-theme="c" data-dividertheme="d">
+					<li data-role="list-divider">API</li>
+					<li><a href="../../docs/api/globalconfig.html">Configuring defaults</a></li>
+					<li><a href="../../docs/api/events.html">Events</a></li>
+					<li><a href="../../docs/api/methods.html">Methods &amp; Utilities</a></li>
+					<li data-theme="a"><a href="../../docs/api/mediahelpers.html">Responsive Layout</a></li>
+					<li><a href="../../docs/api/data-attributes.html">Data attribute reference</a></li>
+					<li><a href="../../docs/api/themes.html">Theme framework</a></li>
+				</ul>
+		</div>
+	</div>
+</div><!-- /content -->
+<div data-role="footer" class="footer-docs" data-theme="c">
+		<p>&copy; 2011-12 The jQuery Foundation</p>
+</div>
+</div><!-- /page -->
+</body>
+</html>

data/lib/ruby_app/resources/elements/mobile/document/jquery.mobile-1.1.0/demos/docs/api/methods.html ADDED

@@ -0,0 +1,597 @@
+<!DOCTYPE html>
+<html>
+	<head>
+	<meta charset="utf-8">
+	<meta name="viewport" content="width=device-width, initial-scale=1">
+	<title>jQuery Mobile Docs - Methods</title>
+	<link rel="stylesheet"  href="../../css/themes/default/jquery.mobile-1.1.0.css" />
+	<link rel="stylesheet" href="../_assets/css/jqm-docs.css"/>
+	<script src="../../js/jquery.js"></script>
+	<script src="../../docs/_assets/js/jqm-docs.js"></script>
+	<script src="../../js/jquery.mobile-1.1.0.js"></script>
+</head>
+<body>
+<div data-role="page" class="type-interior">
+	<div data-role="header" data-theme="f">
+		<h1>Methods</h1>
+		<a href="../../" data-icon="home" data-iconpos="notext" data-direction="reverse">Home</a>
+		<a href="../nav.html" data-icon="search" data-iconpos="notext" data-rel="dialog" data-transition="fade">Search</a>
+	</div><!-- /header -->
+	<div data-role="content">
+	<div class="content-primary">
+	  <p>jQuery Mobile exposes several methods and properties on the $.mobile object for use in your applications.</p>
+		<dl>
+			<dt><code>$.mobile.changePage</code> (<em>method</em>)</dt>
+			<dd>Programmatically change from one page to another. This method is used internally for the page loading and transitioning that occurs as a result of clicking a link or submitting a form, when those features are enabled.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Arguments</dt>
+					<dd><code>to</code> (<em>string or object</em>, required)
+<ul>
+				<li>String: Absolute or relative URL. (&quot;about/us.html&quot;)</li>
+							<li>Object: jQuery collection object. (<code>$("#about")</code>)</li>
+						</ul>
+					</dd>
+					<dd><code>options</code> (<em>object</em>, optional)
+						<ul>
+							<li>Properties:
+								<ul>
+									<li><code>allowSamePageTransition</code> (<em>boolean</em>,	default:	false) By default, changePage() ignores requests to change to the current active page. Setting this option to true, allows the request to execute. Developers should note that some of the page transitions assume that the fromPage and toPage of a changePage request are different, so they may not animate as expected. Developers are responsible for either providing a proper transition, or turning it off for this specific case.</li>
+									<li><code>changeHash</code> (<em>boolean</em>,	default:	true) Decides if the hash in the location bar should be updated. </li>
+									<li><code>data</code> (<em>object</em> or	string,	default: undefined) The data to send with an Ajax page request.
+										<ul>
+											<li>Used only when the 'to' argument of changePage() is a URL.</li>
+										</ul>
+								  </li>
+									<li><code>dataUrl</code> (string,	default: undefined) The URL to use when updating the browser location upon changePage completion.
+								  If not specified, the value of the data-url attribute of the page element is used.</li>
+									<li><code>pageContainer</code> (jQuery collection,	default:	$.mobile.pageContainer) Specifies the element that should contain the page. </li>
+									<li><code>reloadPage</code> (<em>boolean</em>, default: false) Forces a reload of a page, even if it is already in the DOM of the page container.
+										<ul>
+											<li>Used only when the 'to' argument of changePage() is a URL.</li>
+										</ul>
+									</li>
+								  <li><code>reverse</code> (<em>boolean</em>,	default:	false) Decides what direction the transition will run when showing the page. </li>
+									<li><code>showLoadMsg</code> (<em>boolean</em>,	default:	true) Decides whether or not to show the loading message when loading external pages.</li>
+									<li><code>role</code> (<em>string</em>,	default:	undefined) The data-role value to be used when displaying the page. By default this is undefined which means rely on the value of the @data-role attribute defined on the element.</li>
+									<li><code>transition</code> (<em>string</em>,	default:	$.mobile.defaultPageTransition)	The transition to use when showing the page. </li>
+									<li><code>type</code> (<em>string</em>, default: &quot;get&quot;) Specifies the method ("get" or "post") to use when making a page request.
+										<ul>
+											<li>Used only when the 'to' argument of changePage() is a URL.</li>
+										</ul>
+									</li>
+								</ul>
+							</li>
+						</ul>
+					</dd>
+				</dl>
+			</dd>
+			<dd>Examples:
+			<pre>
+			<code>
+<strong>//transition to the "about us" page with a slideup transition</strong>
+$.mobile.changePage( "about/us.html", { transition: "slideup"} );
+<strong>//transition to the "search results" page, using data from a form with an ID of "search"" 	</strong>
+$.mobile.changePage( "searchresults.php", {
+	type: "post",
+	data: $("form#search").serialize()
+});
+<strong>//transition to the "confirm" page with a "pop" transition without tracking it in history	</strong>
+$.mobile.changePage( "../alerts/confirm.html", {
+	transition: "pop",
+	reverse: false,
+	changeHash: false
+});
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.mobile.loadPage</code> (<em>method</em>)</dt>
+			<dd>Load an external page, enhance its content, and insert it into the DOM. This method is called internally by the changePage() function when its first argument is a URL. This function does not affect the current active page so it can be used to load pages in the background. The function returns a deferred promise object that gets resolved after the page has been enhanced and inserted into the document.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Arguments</dt>
+					<dd><code>url</code> (<em>string or object</em>, required) A relative or absolute URL.</dd>
+					<dd><code>options</code> (<em>object</em>, optional)
+						<ul>
+							<li>Properties:
+								<ul>
+									<li><code>data</code> (<em>object</em> or	string,	default: undefined) The data to send with an Ajax page request. </li>
+									<li><code>loadMsgDelay</code> (<em>number (in ms)</em>, default: 50) Forced delay before the loading message is shown. This is meant to allow time for a page that has already been visited to be fetched from cache without a loading message.</li>
+									<li><code>pageContainer</code> (jQuery collection,	default:	$.mobile.pageContainer) Specifies the element that should contain the page after it is loaded. </li>
+									<li><code>reloadPage</code> (<em>boolean</em>, default: false) Forces a reload of a page, even if it is already in the DOM of the page container. </li>
+									<li><code>role</code> (<em>string</em>,	default:	undefined) The data-role value to be used when displaying the page. By default this is undefined which means rely on the value of the @data-role attribute defined on the element.</li>
+									<li><code>type</code> (<em>string</em>, default: &quot;get&quot;) Specifies the method ("get" or "post") to use when making a page request.
+									</li>
+								</ul>
+							</li>
+						</ul>
+					</dd>
+				</dl>
+			</dd>
+			<dd>Examples:
+			<pre>
+			<code>
+<strong>//load the "about us" page into the DOM</strong>
+$.mobile.loadPage( "about/us.html" );
+<strong>//load a "search results" page, using data from a form with an ID of "search"" 	</strong>
+$.mobile.loadPage( "searchresults.php", {
+	type: "post",
+	data: $("form#search").serialize()
+});
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.fn.jqmData(), $.fn.jqmRemoveData()</code> (<em>method</em>)</dt>
+			<dd>When working with jQuery Mobile, <code>jqmData</code> and <code>jqmRemoveData</code> should be used in place of jQuery core's <code>data</code> and <code>removeData</code> methods (note that this includes $.fn.data, $.fn.removeData, and the $.data, $.removeData, and $.hasData utilities), as they automatically incorporate getting and setting of namespaced data attributes (even if no namespace is currently in use).</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Arguments:</dt>
+					<dd>See jQuery's <a href="http://api.jquery.com/jQuery.data/">data</a> and <a href="http://api.jquery.com/jQuery.removeData/">removeData</a> methods</dd>
+					<strong>Note: </strong>Calling jqmData() with no argument will return <code>undefined</code>. This behavior is subject to change in future versions.
+					<dt><code>&#183;</code> Also:</dt>
+					<dd>When finding elements by their jQuery Mobile data attribute, please use the custom selector <code>:jqmData()</code>, as it automatically incorporates namespaced data attributes into the lookup when they are in use. For example, instead of calling <code>$("div[data-role='page']")</code>, you should use <code>$("div:jqmData(role='page')")</code>, which internally maps to <code>$("div[data-"+ $.mobile.ns +"role='page']")</code> without forcing you to concatenate a namespace into your selectors manually.</dd>
+				</dl>
+			</dd>
+			<dt><code>$.fn.jqmEnhanceable()</code> (<em>method</em>)</dt>
+			<dd>For users that wish to respect <code>data-enhance=false</code> parent elements during manual enhancement or custom plugin authoring jQuery Mobile provides the <code>$.fn.jqmEnhanceable</code> filter method.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Settings:</dt>
+					<dd>If, and only if, <code>$.mobile.ignoreContentEnabled</code> is set to true, this method will traverse the parent nodes for each DOM element in the jQuery object and where it finds a <code>data-enhance=false</code> parent the child will be removed from the set.</dd>
+					<dt><code>&#183;</code> Warning:</dt>
+					<dd>The operation of traversing all parent elements can be expensive for even small jQuery object sets.</dd>
+				</dl>
+			</dd>
+			<dt><code>$.fn.jqmHijackable()</code> (<em>method</em>)</dt>
+			<dd>For users that wish to respect <code>data-ajax=false</code> parent elements during custom form and link binding jQuery Mobile provides the <code>$.fn.jqmHijackable</code> filter method.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Settings:</dt>
+					<dd>If, and only if, <code>$.mobile.ignoreContentEnabled</code> is set to true, this method will traverse the parent nodes for each DOM element in the jQuery object and where it finds a <code>data-ajax=false</code> parent the child form or link will be removed from the set.</dd>
+					<dt><code>&#183;</code> Warning:</dt>
+					<dd>The operation of traversing all parent elements can be expensive for even small jQuery object sets.</dd>
+				</dl>
+			</dd>
+			<dt><code>$.mobile.showPageLoadingMsg</code> (<em>method</em>)</dt>
+			<dd>Show the page loading message, which is configurable via $.mobile.loadingMessage.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Arguments</dt>
+					<dd><code>theme</code> (<em>string</em>, default: "a") The theme swatch for the message.</dd>
+					<dd><code>msgText</code> (<em>string</em>, default: "loading") The text of the message.</dd>
+					<dd><code>textonly</code> (<em>boolean</em>, default: false) If true, the "spinner" image will be hidden when the message is shown.</dd>
+				</dl>
+			</dd>
+			<dd>Examples:
+			<pre>
+			<code>
+<strong>//cue the page loader</strong>
+$.mobile.showPageLoadingMsg();
+<strong>//use theme swatch "b", a custom message, and no spinner</strong>
+$.mobile.showPageLoadingMsg("b", "This is only a test", true);
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.mobile.hidePageLoadingMsg</code> (<em>method</em>)</dt>
+			<dd>Hide the page loading message, which is configurable via $.mobile.loadingMessage.</dd>
+			<dd>Example:
+			<pre>
+			<code>
+<strong>//hide the page loader</strong>
+$.mobile.hidePageLoadingMsg();
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.mobile.fixedToolbars.show</code> (<em>method</em>)</dt>
+			<dd>Utility method for displaying the fixed header and/or footer of the current active page within the viewport. Note that fixed headers/footers are never really hidden. Toggling the show/hide state of a toolbar is really toggling whether or not they are inline within the page content, or displayed within the viewport as if they were fixed.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Arguments</dt>
+					<dd><code>immediately</code> (<em>boolean</em>, optional) If true, any fixed header or footer for the current active page is displayed immediately within the viewport. If false or unspecified, the fixed header/footer will fade-in after a 100 millisecond delay. Note that other events such as a document resize or scroll event can result in an additional delay before the start of the header/footer display animation.</dd>
+				</dl>
+			</dd>
+			<dd>Example:
+			<pre>
+			<code>
+<strong>// Show fixed header/footer with a fade animation.</strong>
+$.mobile.fixedToolbars.show();
+<strong>// Show fixed header/footer immediately.</strong>
+$.mobile.fixedToolbars.show(true);
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.mobile.fixedToolbars.hide</code> (<em>method</em>)</dt>
+			<dd>Utility method for hiding the fixed header and/or footer of the current active page.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Arguments</dt>
+					<dd><code>immediately</code> (<em>boolean</em>, optional) If true, any fixed header or footer for the current active page is immediately placed inline (back in flow) with the page content, which means it will scroll along with the content and will only be visible when viewing the top or bottom of the page within the viewport. If false or unspecified, the fixed header/footer will fade-out after a 100 millisecond delay. Note that other events such as a document resize or scroll event can result in the header/footer being immediately hidden.</dd>
+				</dl>
+			</dd>
+			<dd>Example:
+			<pre>
+			<code>
+<strong>// Hide fixed header/footer with a fade animation.</strong>
+$.mobile.fixedToolbars.hide();
+<strong>// Hide fixed header/footer immediately.</strong>
+$.mobile.fixedToolbars.hide(true);
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.mobile.path.parseUrl</code> (<em>method</em>)</dt>
+			<dd>Utility method for parsing a URL and its relative variants into an object that makes accessing the components of the URL easy. When parsing relative variants, the resulting object will contain empty string values for missing components (like protocol, host, etc). Also, when parsing URLs that have no authority, such as tel: urls, the pathname property of the object will contain the data after the protocol/scheme colon.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Arguments</dt>
+					<dd><code>url</code> (<em>string</em>, required) A relative or absolute URL.</dd>
+					<dt><code>&#183;</code> Return Value</dt>
+					<dd>
+						<p>This function returns an object that contains the various components of the URL as strings. The properties on the object mimic the browser's location object:</p>
+						<dl>
+							<dt><code>hash</code></dt>
+							<dd>The fragment conponent of the URL, including the leading '#' character.</dd>
+							<dt><code>host</code></dt>
+							<dd>The host and port number of the URL.</dd>
+							<dt><code>hostname</code></dt>
+							<dd>The name of the host within the URL.</dd>
+							<dt><code>href</code></dt>
+							<dd>The original URL that was parsed.</dd>
+							<dt><code>pathname</code></dt>
+							<dd>The path of the file or directory referenced by the URL.</dd>
+							<dt><code>port</code></dt>
+							<dd>The port specified within the URL. Most URLs rely on the default port for the protocol used, so this may be an empty string most of the time.</dd>
+							<dt><code>protocol</code></dt>
+							<dd>The protocol for the URL including the trailing ':' character.</dd>
+							<dt><code>search</code></dt>
+							<dd>The query component of the URL including the leading '?' character.</dd>
+						</dl>
+						<p>But it also contains additional properties that provide access to additional components as well as some common forms of the URL developers access:</p>
+						<dl>
+							<dt><code>authority</code></dt>
+							<dd>The username, password, and host components of the URL</dd>
+							<dt><code>directory</code></dt>
+							<dd>The directory component of the pathname, minus any filename.</dd>
+							<dt><code>domain</code></dt>
+							<dd>The protocol and authority components of the URL.</dd>
+							<dt><code>filename</code></dt>
+							<dd>The filename within the pathname component, minus the directory.</dd>
+							<dt><code>hrefNoHash</code></dt>
+							<dd>The original URL minus the fragment (hash) components.</dd>
+							<dt><code>hrefNoSearch</code></dt>
+							<dd>The original URL minus the query (search) and fragment (hash) components.</dd>
+							<dt><code>password</code></dt>
+							<dd>The password contained within the authority component.</dd>
+							<dt><code>username</code></dt>
+							<dd>The username contained within the authority component.</dd>
+						</dl>
+					</dd>
+				</dl>
+			</dd>
+			<dd>Examples:
+			<pre>
+			<code>
+<strong>// Parsing the Url below results an object that is returned with the
+// following properties:
+//
+//  obj.href:         http://jblas:password@mycompany.com:8080/mail/inbox?msg=1234&amp;type=unread#msg-content
+//  obj.hrefNoHash:   http://jblas:password@mycompany.com:8080/mail/inbox?msg=1234&amp;type=unread
+//  obj.hrefNoSearch: http://jblas:password@mycompany.com:8080/mail/inbox
+//  obj.domain:       http://jblas:password@mycompany.com:8080
+//  obj.protocol:     http:
+//  obj.authority:    jblas:password@mycompany.com:8080
+//  obj.username:     jblas
+//  obj.password:     password
+//  obj.host:         mycompany.com:8080
+//  obj.hostname:     mycompany.com
+//  obj.port:         8080
+//  obj.pathname:     /mail/inbox
+//  obj.directory:    /mail/
+//  obj.filename:     inbox
+//  obj.search:       ?msg=1234&amp;type=unread
+//  obj.hash:         #msg-content</strong>
+var obj = $.mobile.path.parseUrl("http://jblas:password@mycompany.com:8080/mail/inbox?msg=1234");
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.mobile.path.makePathAbsolute</code> (<em>method</em>)</dt>
+			<dd>Utility method for converting a relative file or directory path into an absolute path.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Arguments</dt>
+					<dd><code>relPath</code> (<em>string</em>, required) A relative file or directory path.</dd>
+					<dd><code>absPath</code> (<em>string</em>, required) An absolute file or relative path to resolve against.</dd>
+					<dt><code>&#183;</code> Return Value</dt>
+					<dd>This function returns a string that is an absolute version of the relative path passed in.</dd>
+				</dl>
+			</dd>
+			<dd>Examples:
+			<pre>
+			<code>
+<strong>// Returns: /a/b/c/file.html</strong>
+var absPath = $.mobile.path.makePathAbsolute("file.html", "/a/b/c/bar.html");
+<strong>// Returns: /a/foo/file.html</strong>
+var absPath = $.mobile.path.makePathAbsolute("../../foo/file.html", "/a/b/c/bar.html");
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.mobile.path.makeUrlAbsolute</code> (<em>method</em>)</dt>
+			<dd>Utility method for converting a relative URL to an absolute URL.</dd>
+			<dd>
+				<dl>
+					<dt>Arguments</dt>
+					<dd><code>relUrl</code> (<em>string</em>, required) A relative URL.</dd>
+					<dd><code>absUrl</code> (<em>string</em>, required) An absolute URL to resolve against.</dd>
+					<dt>Return Value</dt>
+					<dd>This function returns a string that is an absolute version of the relative URL passed in.</dd>
+				</dl>
+			</dd>
+			<dd>Examples:
+			<pre>
+			<code>
+<strong>// Returns: http://foo.com/a/b/c/file.html</strong>
+var absUrl = $.mobile.path.makeUrlAbsolute("file.html", "http://foo.com/a/b/c/test.html");
+<strong>// Returns: http://foo.com/a/foo/file.html</strong>
+var absUrl = $.mobile.path.makeUrlAbsolute("../../foo/file.html", "http://foo.com/a/b/c/test.html");
+<strong>// Returns: http://foo.com/bar/file.html</strong>
+var absUrl = $.mobile.path.makeUrlAbsolute("//foo.com/bar/file.html", "http://foo.com/a/b/c/test.html");
+<strong>// Returns: http://foo.com/a/b/c/test.html?a=1&amp;b=2</strong>
+var absUrl = $.mobile.path.makeUrlAbsolute("?a=1&amp;b=2", "http://foo.com/a/b/c/test.html");
+<strong>// Returns: http://foo.com/a/b/c/test.html#bar</strong>
+var absUrl = $.mobile.path.makeUrlAbsolute("#bar", "http://foo.com/a/b/c/test.html");
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.mobile.path.isSameDomain</code> (<em>method</em>)</dt>
+			<dd>Utility method for comparing the domain of 2 URLs.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Arguments</dt>
+					<dd><code>url1</code> (<em>string</em>, required) A relative URL.</dd>
+					<dd><code>url2</code> (<em>string</em>, required) An absolute URL to resolve against.</dd>
+					<dt>Return Value</dt>
+					<dd>This function returns a boolean true if the domains match, false if they don't.</dd>
+				</dl>
+			</dd>
+			<dd>Examples:
+			<pre>
+			<code>
+<strong>// Returns: true</strong>
+var same = $.mobile.path.isSameDomain("http://foo.com/a/file.html", "http://foo.com/a/b/c/test.html");
+<strong>// Returns: false</strong>
+var same = $.mobile.path.isSameDomain("file://foo.com/a/file.html", "http://foo.com/a/b/c/test.html");
+<strong>// Returns: false</strong>
+var same = $.mobile.path.isSameDomain("https://foo.com/a/file.html", "http://foo.com/a/b/c/test.html");
+<strong>// Returns: false</strong>
+var same = $.mobile.path.isSameDomain("http://foo.com/a/file.html", "http://bar.com/a/b/c/test.html");
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.mobile.path.isRelativeUrl</code> (<em>method</em>)</dt>
+			<dd>Utility method for determining if a URL is a relative variant.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Arguments</dt>
+					<dd><code>url</code> (<em>string</em>, required) A relative or absolute URL.</dd>
+					<dt><code>&#183;</code> Return Value</dt>
+					<dd>This function returns a boolean true if the URL is relative, false if it is absolute.</dd>
+				</dl>
+			</dd>
+			<dd>Examples:
+			<pre>
+			<code>
+<strong>// Returns: false</strong>
+var isRel = $.mobile.path.isRelativeUrl("http://foo.com/a/file.html");
+<strong>// Returns: true</strong>
+var isRel = $.mobile.path.isRelativeUrl("//foo.com/a/file.html");
+<strong>// Returns: true</strong>
+var isRel = $.mobile.path.isRelativeUrl("/a/file.html");
+<strong>// Returns: true</strong>
+var isRel = $.mobile.path.isRelativeUrl("file.html");
+<strong>// Returns: true</strong>
+var isRel = $.mobile.path.isRelativeUrl("?a=1&amp;b=2");
+<strong>// Returns: true</strong>
+var isRel = $.mobile.path.isRelativeUrl("#foo");
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.mobile.path.isAbsoluteUrl</code> (<em>method</em>)</dt>
+			<dd>Utility method for determining if a URL is absolute.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Arguments</dt>
+					<dd><code>url</code> (<em>string</em>, required) A relative or absolute URL.</dd>
+					<dt><code>&#183;</code> Return Value</dt>
+					<dd>This function returns a boolean true if the URL is absolute, false if not.</dd>
+				</dl>
+			</dd>
+			<dd>Examples:
+			<pre>
+			<code>
+<strong>// Returns: true</strong>
+var isAbs = $.mobile.path.isAbsoluteUrl("http://foo.com/a/file.html");
+<strong>// Returns: false</strong>
+var isAbs = $.mobile.path.isAbsoluteUrl("//foo.com/a/file.html");
+<strong>// Returns: false</strong>
+var isAbs = $.mobile.path.isAbsoluteUrl("/a/file.html");
+<strong>// Returns: false</strong>
+var isAbs = $.mobile.path.isAbsoluteUrl("file.html");
+<strong>// Returns: false</strong>
+var isAbs = $.mobile.path.isAbsoluteUrl("?a=1&amp;b=2");
+<strong>// Returns: false</strong>
+var isAbs = $.mobile.path.isAbsoluteUrl("#foo");
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.mobile.base</code> (<em>methods, properties</em>)</dt>
+			<dd>Utilities for working with generated base element. TODO: document as public API is finalized.</dd>
+			<dt><code>$.mobile.silentScroll</code> (<em>method</em>)</dt>
+			<dd>Scroll to a particular Y position without triggering scroll event listeners.</dd>
+			<dd>
+				<dl>
+					<dt><code>&#183;</code> Arguments:</dt>
+					<dd><code>yPos</code> (<em>number</em>, defaults to 0). Pass any number to scroll to that Y location.</dd>
+				</dl>
+			</dd>
+			<dd>Examples:
+			<pre>
+			<code>
+<strong>//scroll to Y 100px</strong>
+$.mobile.silentScroll(100);
+			</code>
+			</pre>
+			</dd>
+			<dt><code>$.mobile.activePage</code> (<em>property</em>)</dt>
+			<dd>Reference to the page currently in view.</dd>
+		</dl>
+	</div><!--/content-secondary -->
+	<div class="content-secondary">
+		<div data-role="collapsible" data-collapsed="true" data-theme="b" data-content-theme="d">
+				<h3>More in this section</h3>
+				<ul data-role="listview"  data-theme="c" data-dividertheme="d">
+					<li data-role="list-divider">API</li>
+					<li><a href="../../docs/api/globalconfig.html">Configuring defaults</a></li>
+					<li><a href="../../docs/api/events.html">Events</a></li>
+					<li data-theme="a"><a href="../../docs/api/methods.html">Methods &amp; Utilities</a></li>
+					<li><a href="../../docs/api/data-attributes.html">Data attribute reference</a></li>
+					<li><a href="../../docs/api/themes.html">Theme framework</a></li>
+				</ul>
+		</div>
+	</div>
+</div><!-- /content -->
+<div data-role="footer" class="footer-docs" data-theme="c">
+		<p>&copy; 2011-12 The jQuery Foundation</p>
+</div>
+</div><!-- /page -->
+</body>
+</html>