Skip to content

Commit

Permalink
merged with trunk
Browse files Browse the repository at this point in the history
  • Loading branch information
@hpbuniat
hpbuniat committed Oct 5, 2011
1 parent 67c18c8 commit f356a38
Show file tree
Hide file tree
Showing 178 changed files with 3,473 additions and 2,630 deletions.
1 change: 0 additions & 1 deletion Makefile
View file
Expand Up @@ -68,7 +68,6 @@ JSFILES = js/jquery.ui.widget.js \
js/jquery.mobile.links.js \
js/jquery.mobile.fixHeaderFooter.js \
js/jquery.mobile.fixHeaderFooter.native.js \
js/jquery.mobile.media.classes.js \
js/jquery.mobile.init.js

# The files to include when compiling the CSS files
Expand Down
4 changes: 3 additions & 1 deletion README.md
View file
Expand Up @@ -23,7 +23,9 @@ A full, complete version and a minified, complete version of the jQuery Mobile J
Submitting bugs
===================================

If you think you've found a bug, please visit the Issue tracker (https://github.com/jquery/jquery-mobile/issues) and create an issue explaining the problem and expected result. Be sure to include any relevant information for reproducing the issue, such as the browser/device (with version #), and the version of the jQuery Mobile code you're running. It also helps a lot to make sure that the bug still exists on jquerymobile.com/test/, as it's possible we may have fixed it already! It is also best to include code to reproduce the bug.
If you think you've found a bug, please visit the Issue tracker (https://github.com/jquery/jquery-mobile/issues) and create an issue explaining the problem and expected result. Be sure to include any relevant information for reproducing the issue, such as the browser/device (with version #), and the version of the jQuery Mobile code you're running. It also helps a lot to make sure that the bug still exists on http://jquerymobile.com/test/, as it's possible we may have fixed it already!

It is also best to include code to reproduce the bug. To do that please use [jsbin](http://jsbin.com) or [jsfiddle](http://jsfiddle.net) and include a link to it in the ticket.


Submitting patches
Expand Down
1 change: 0 additions & 1 deletion build.xml
View file
Expand Up @@ -52,7 +52,6 @@
jquery.mobile.links.js,
jquery.mobile.fixHeaderFooter.js,
jquery.mobile.fixHeaderFooter.native.js,
jquery.mobile.media.classes.js,
jquery.mobile.init.js"/>

<target name="merge">
Expand Down
22 changes: 14 additions & 8 deletions docs/_assets/css/jqm-docs.css
View file
Expand Up @@ -63,18 +63,17 @@ p.intro strong {
padding-bottom: 0;
}
.content-secondary .ui-collapsible {
padding: 10px 15px;
padding: 0 15px 10px;

}
.content-secondary .ui-collapsible-heading {
margin: 0 0 30px;
}
.content-secondary .ui-collapsible-heading-collapsed,
.content-secondary .ui-collapsible-content {
padding:0;
padding: 0;
background: none;
border-bottom: none;
}
.content-secondary .ui-listview {
margin: 0;
}

/* new API additions */

dt {
Expand Down Expand Up @@ -181,17 +180,24 @@ dd h4 { margin:15px 0 0 0; }
float: left;
width: 45%;
background: none;
border-top: 0;
}
.content-secondary,
.type-interior .content-secondary {
margin: 30px 0 20px 2%;
padding: 20px 4% 0 0;
background: none;
border-top: none;
}
.type-index .content-secondary {
padding: 0;
}
.content-secondary .ui-collapsible {
margin: 0;
padding: 0;
}
.content-secondary .ui-collapsible-content {
border: none;
}
.type-index .content-secondary .ui-listview {
margin: 0;
}
Expand Down
Binary file removed docs/_assets/images/ipad-palm.png
View file
Binary file not shown.
Binary file modified docs/_assets/images/version.png
View file
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 1 addition & 1 deletion docs/about/accessibility.html
View file
Expand Up @@ -36,7 +36,7 @@ <h2>Accessibility</h2>

<div class="content-secondary">

<div data-role="collapsible" data-collapsed="true" data-theme="b">
<div data-role="collapsible" data-collapsed="true" data-theme="b" data-content-theme="d">

<h3>More in this section</h3>

Expand Down
14 changes: 8 additions & 6 deletions docs/about/features.html
View file
Expand Up @@ -26,15 +26,17 @@ <h1>Features</h1>

<h2>Key features:</h2>
<ul>
<li><strong>Built on jQuery core</strong> for familiar and consistent jQuery syntax and minimal learning curve</li>
<li><strong>Compatible with all major mobile & desktop platforms</strong> - iOS, Android, Blackberry, Palm WebOS, Nokia/Symbian, Windows Mobile, Opera Mobile/Mini, Firefox Mobile and all modern desktop browsers.</li>
<li><strong>Lightweight size</strong> (~20k compressed for all mobile functionality) and minimal image dependencies for speed.</li>
<li><strong>Built on jQuery core</strong> for familiar and consistent jQuery syntax and minimal learning curve and leverages jQuery UI code and patterns.</li>
<li><strong>Compatible with all major mobile, tablet, e-reader & desktop platforms</strong> - iOS, Android, Blackberry, Palm WebOS, Nokia/Symbian, Windows Phone 7, MeeGo, Opera Mobile/Mini, Firefox Mobile, Kindle, Nook, and all modern browsers with graded levels of support.</li>
<li><strong>Lightweight size</strong> and minimal image dependencies for speed.</li>
<li><strong>Modular architecture</strong> for creating custom builds that are optimized to only the features needed for a particular application</li>
<li><strong>HTML5 Markup-driven configuration</strong> of pages and behavior for fast development and minimal required scripting.</li>
<li><strong>Progressive enhancement</strong> approach brings core content and functionality to all mobile, tablet and desktop platforms and a rich, installed application-like experience on newer mobile platforms.</li>
<li><strong>Automatic initialization</strong> by using HTML5 <code> data-role</code> attributes in the HTML markup to act as the trigger to automatically initialize all jQuery Mobile widgets found on a page.</li>
<li><strong>Responsive design</strong> techniques and tools allow the same underlying codebase to automatically scale from smartphone to desktop-sized screens</li>
<li><strong>Powerful Ajax-powered navigation system</strong> to enable animated page transitions while maintaining back button, bookmarking and and clean URLs though pushState. </li>
<li><strong>Accessibility</strong> features such as WAI-ARIA are also included to ensure that the pages work for screen readers (e.g. VoiceOver in iOS) and other assistive technologies.</li>
<li><strong>Touch and mouse event support</strong> streamline the process of supporting touch, mouse, and cursor focus-based user input methods with a simple API. </li>
<li><strong>UI widgets</strong> enhance native controls with touch-optimized, themable controls. </li>
<li><strong>Unified UI widgets</strong> for common controls enhance native controls with touch-optimized, themable controls that are platform-agnostic and easy to use.</li>
<li><strong>Powerful theming framework</strong> and ThemeRoller application make highly-branded experiences easy to build.</li>

</ul>
Expand All @@ -43,7 +45,7 @@ <h2>Key features:</h2>

<div class="content-secondary">

<div data-role="collapsible" data-collapsed="true" data-theme="b">
<div data-role="collapsible" data-collapsed="true" data-theme="b" data-content-theme="d">

<h3>More in this section</h3>

Expand Down
3 changes: 1 addition & 2 deletions docs/about/intro.html
View file
Expand Up @@ -34,13 +34,12 @@ <h2>jQuery Mobile Overview</h2>

<p>To make this broad support possible, all pages in jQuery Mobile are built on a foundation of <strong>clean, semantic HTML</strong> to ensure compatibility with pretty much any web-enabled device. In devices that interpret CSS and JavaScript, jQuery Mobile applies <strong>progressive enhancement techniques</strong> to unobtrusively transform the semantic page into a rich, interactive experience that leverages the power of jQuery and CSS. <strong>Accessibility features</strong> such as WAI-ARIA are tightly integrated throughout the framework to provide support for screen readers and other assistive technologies.</p>

<img src="../_assets/images/ipad-palm.png" alt="Smartphone and tablet designs" style="max-width:100%; margin-top:20px;">

</div><!--/content-primary -->

<div class="content-secondary">

<div data-role="collapsible" data-collapsed="true" data-theme="b">
<div data-role="collapsible" data-collapsed="true" data-theme="b" data-content-theme="d">

<h3>More in this section</h3>

Expand Down
49 changes: 24 additions & 25 deletions docs/about/platforms.html
View file
Expand Up @@ -24,56 +24,55 @@ <h1>Supported platforms</h1>


<div class="content-primary">
<h2 id="platforms">Platform support in Beta 3</h2>
<p>As of Beta 3, we've pretty much covered our target platforms for 1.0. At this stage, jQuery Mobile works on the vast majority of all modern desktop, smartphone, tablet, and e-reader platforms. In addition, feature phones and older browsers are also supported because of our progressive enhancement approach. We're very proud of our commitment to universal accessibility through our broad support for all popular platforms.</p>
<h2 id="platforms">Platform support in 1.0 RC1</h2>
<p>We're excited to announce that as of 1.0 RC1, we've covered all our target platforms for the project. At this stage, we have broad support for the vast majority of all modern desktop, smartphone, tablet, and e-reader platforms. In addition, feature phones and older browsers are supported because of our progressive enhancement approach. We're very proud of our commitment to universal accessibility through our broad support for all popular platforms.</p>

<p>Our <a href="http://jquerymobile.com/gbs/">graded support matrix</a> was created over a year ago based on our goals as a project and since that time, we've been refining our grading system based on real-world device testing and the quickly evolving mobile landscape. To provide a quick summary of our browser support in Beta 1, we've created a simple A (full), B (full minus Ajax), C (basic) grade system with notes of the actual devices and versions we've been testing on in our lab.</p>

<p>The visual fidelity of the experience is highly dependent on CSS rendering capabilities of the device and platform so not all A grade experience will be pixel-perfect but that's the nature of the web. We'll be adding additional vendor-prefixed CSS rules to bring transitions, gradients and other visual improvements to non-WebKit browsers in future releases so look for even more added visual polish as we move towards 1.0.</p>
<p>The visual fidelity of the experience is highly dependent on CSS rendering capabilities of the device and platform so not all A grade experience will be pixel-perfect but that's the nature of the web. </p>
<h3 style="display: block; font-size: 15px !important; font-weight: normal; background: #f0f0f0; border-left: 7px solid #74B64A; padding: 5px 0 5px 8px;"><strong> A-grade</strong> - Full enhanced experience with Ajax-based animated page transitions.</h3>
<ul>
<li><strong>Apple iOS 3.2-5.0 beta</strong>: Tested on the original iPad (3.2 / 4.3), iPad 2 (4.3), original iPhone (3.1), iPhone 3 (3.2), 3GS (4.3), and 4 (4.3 / 5.0 beta)</li>
<li><strong>Android 2.1-2.3</strong>: Tested on the HTC Incredible (2.2), original Droid (2.2), Nook Color (2.2), HTC Aria (2.1), Google Nexus S (2.3). Functional on 1.5 &amp; 1.6 but performance may be sluggish, tested on Google G1 (1.5)</li>
<li><strong>Android Honeycomb</strong>: Tested on the Samsung Galaxy Tab 10.1</li>
<li><strong>Windows Phone 7</strong>: Tested on the HTC 7 Surround</li>
<li><strong>Blackberry 6.0</strong>: Tested on the Torch 9800 and Style 9670</li>
<li><strong>Blackberry 7</strong>: <span style="background: yellow; padding: 2px 5px; font-size: 10px;">NEW</span> Tested on BlackBerry Torch 9810</li>
<li><strong>Blackberry Playbook</strong>: Tested on PlayBook version 1.0.1 / 1.0.5</li>
<li><strong>Palm WebOS (1.4-2.0)</strong>: Tested on the Palm Pixi (1.4), Pre (1.4), Pre 2 (2.0)</li>
<li><strong>Palm WebOS 3.0 </strong>- Tested on HP TouchPad</li>
<li><strong>Meego 1.2</strong>: <span style="background: yellow; padding: 2px 5px; font-size: 10px;">NEW</span> Tested on the Nokia N950</li>
<li><strong>Firebox Mobile (Beta)</strong>: Tested on Android 2.2</li>
<li><strong>Apple iOS 3.2-5.0 beta</strong> - Tested on the original iPad (3.2 / 4.3), iPad 2 (4.3), original iPhone (3.1), iPhone 3 (3.2), 3GS (4.3), and 4 (4.3 / 5.0 beta)</li>
<li><strong>Android 2.1-2.3</strong> - Tested on the HTC Incredible (2.2), original Droid (2.2), Nook Color (2.2), HTC Aria (2.1), Google Nexus S (2.3). Functional on 1.5 &amp; 1.6 but performance may be sluggish, tested on Google G1 (1.5)</li>
<li><strong>Android Honeycomb</strong>- Tested on the Samsung Galaxy Tab 10.1</li>
<li><strong>Windows Phone 7</strong> - Tested on the HTC 7 Surround</li>
<li><strong>Blackberry 6.0</strong> - Tested on the Torch 9800 and Style 9670</li>
<li><strong>Blackberry 7</strong> - Tested on BlackBerry® Torch 9810</li>
<li><strong>Blackberry Playbook</strong> - Tested on PlayBook version 1.0.1 / 1.0.5</li>
<li><strong>Palm WebOS (1.4-2.0)</strong> - Tested on the Palm Pixi (1.4), Pre (1.4), Pre 2 (2.0)</li>
<li><strong>Palm WebOS 3.0 </strong> - Tested on HP TouchPad</li>
<li><strong>Firebox Mobile (Beta)</strong> - Tested on Android 2.2</li>
<li><strong>Opera Mobile 11.0</strong>: Tested on the iPhone 3GS and 4 (5.0/6.0), Android 2.2 (5.0/6.0), Windows Mobile 6.5 (5.0)</li>
<li><strong>Meego 1.2</strong> <span style="background: yellow; padding: 2px 5px; font-size: 10px;">NEW</span> - Tested on Nokia 950</li>
<li><strong>Kindle 3</strong>: Tested on the built-in WebKit browser included in the Kindle 3 device</li>
<li><strong>Chrome <strong>Desktop </strong>11-13</strong>: Tested on OS X 10.6.7 and Windows 7</li>
<li><strong>Firefox Desktop 3.6-4.0</strong>: Tested on OS X 10.6.7 and Windows 7</li>
<li><strong>Internet Explorer 7-9</strong> : Tested on Windows XP, Vista and 7 (minor CSS issues)</li>
<li><strong>Opera Desktop 10-11</strong>: Tested on OS X 10.6.7 and Windows 7</li>
<li><strong>Chrome <strong>Desktop </strong>11-13</strong> - Tested on OS X 10.6.7 and Windows 7</li>
<li><strong>Firefox Desktop 3.6-4.0</strong> - Tested on OS X 10.6.7 and Windows 7</li>
<li><strong>Internet Explorer 7-9</strong> - Tested on Windows XP, Vista and 7 (minor CSS issues)</li>
<li><strong>Opera Desktop 10-11</strong> - Tested on OS X 10.6.7 and Windows 7</li>
</ul>
<h3 style="display: block; font-size: 15px !important; font-weight: normal; background: #f0f0f0; border-left: 7px solid #6699cc; padding: 5px 0 5px 8px;"><strong>B-grade</strong> - Enhanced experience except without Ajax navigation features.</h3>
<ul>
<li><strong>Blackberry 5.0</strong>: Tested on the Storm 2 9550, Bold 9770</li>
<li><strong>Opera Mini (5.0-6.0)</strong>: Tested on iOS 3.2/4.3</li>
<li><strong>Windows Phone 6.5</strong>: Tested on the HTC</li>
<li><strong>Nokia Symbian^3 </strong>: Tested on Nokia N8 (Symbian^3), C7 (Symbian^3), also works on N97 (Symbian^1)</li>
<li><strong>Opera Mini (5.0-6.0)</strong> - Tested on iOS 3.2/4.3</li>
<li><strong>Nokia Symbian^3 </strong>- Tested on Nokia N8 (Symbian^3), C7 (Symbian^3), also works on N97 (Symbian^1)</li>
</ul>
<h3 style="display: block; font-size: 15px !important; font-weight: normal; background: #f0f0f0; border-left: 7px solid #FFCC33; padding: 5px 0 5px 8px;"><strong>C<strong>-grade</strong></strong> - Basic, non-enhanced HTML experience that is still functional</h3>
<ul>
<li><strong>Blackberry4.x</strong>: Tested on the Curve 8330</li>
<li><strong>Blackberry 4.x</strong> - Tested on the Curve 8330</li>
<li><strong>Windows Mobile</strong> - Tested on the HTC Leo (WInMo 5.2)</li>
<li><strong>All older smartphone platforms and featurephones</strong> - Any device that doesn't support media queries will receive the basic, C grade experience</li>
</ul>
<h3 style="display: block; font-size: 15px !important; font-weight: normal; background: #f0f0f0; border-left: 7px solid #aaaaaa; padding: 6px 0 8px 8px;"><strong>Not Officially Supported - </strong>May work, but haven't been thoroughly tested or debugged</h3>
<ul>
<li><strong>Samsung Bada</strong> - The project doesn't currently have test devices or emulators, but current support is known to be fairly good. Support level undecided for 1.0.</li>
<li><strong>Samsung Bada</strong> - The project doesn't currently have test devices or emulators, but current support is known to be fairly good. Support level undecided for 1.0</li>
</ul>



</div>

<div class="content-secondary">

<div data-role="collapsible" data-collapsed="true" data-theme="b">
<div data-role="collapsible" data-collapsed="true" data-theme="b" data-content-theme="d">

<h3>More in this section</h3>

Expand Down

0 comments on commit f356a38

Please sign in to comment.