1. added the $.mobile object, for storing public options used in core and other plugins that should be made configurable externally, somehow. 2. With this change comes the first property $.mobile: subPageUrlKey, which defaults to "ui-page" and becomes the URL parameter for denoting a generated sub-page of a particular URL. For example, you can now deep-link to sub-levels of a nested listview like this: jquerymobile.com/test/#_listview.html&ui-page=listview-2 ...in which "listview-2" refers to a generated page created by _listview.html when mobilize() runs on it. Note that this &ui-page parameter is used for splitting the hash to find the right part to use for the ajax request for the real url (_listview.html), while the ID of the actual subpage div really uses the whole thing: "_listview.html&ui-page=listview-2". The other idea is that after the "&ui-page=" part, plugins should use an ID that reflects their widget name. For example, &ui-page=listview-2 or &ui-page=globalnav. Before this change, subpages would use the whole hash without mentioning their parent page url, so you'd end up with blank pages if you hit refresh while viewing a generated sub-page. |
||
|---|---|---|
| css | ||
| experiments | ||
| images | ||
| js | ||
| sample-content | ||
| .htaccess | ||
| _containers-states.html | ||
| _dialog.html | ||
| _events.html | ||
| _fixed-variation1.html | ||
| _fixed-variation2.html | ||
| _fixed.html | ||
| _form-controls.html | ||
| _globalnav-glyphish.html | ||
| _globalnav.html | ||
| _listview.html | ||
| _search-results.html | ||
| _search.html | ||
| _transitions-destination.html | ||
| _transitions.html | ||
| combine.php | ||
| index.html | ||
| README.md | ||
Early stage development for the jQuery Mobile UI Framework. Code is subject to change dramatically!
Usage
For now, I've set things up with a little combinator script to concat all the css and js files into one request and gzip. (js/all and css/all) You'll need to point your local apache & php webserver at this root directory in order to preview things.
If you don't currently have a webserver running locally, a quick way to get up and running is to download and install Mamp for Mac OSX. Once installed, just open Mamp, click preferences, go to the Apache tab, and select your local jQuery Mobile folder as the root. Then you can open a browser to http://localhost:8888 to preview the code. An alternative is XAMPP, which is also available for Windows, though you need to actually modify Apache's httpd.conf to point to your checkout: http://www.apachefriends.org/en/xampp.html You need the Rewrite (mod_rewrite.so), Expire (mod_expires.so) and Header (mod_headers.so) modules loaded.
Whenever this configuration becomes inconvenient, we can remove it, obviously it's not meant to stay!
- when adding a js or css file, add it to the manifest in its directory and it'll be included in the request
- As far as JS files go, jQuery.mobile.js is the starting point.