组织 jQuery Mobile 应用程序的最佳实践是什么?

使用多个单个 HTML 页面，大型多页面模板会抵消 jQM ajax 加载的好处，因为您在开始时加载所有 HTML(除非您的网站很小)

Use multiple single HTML pages, a large multi-page template defeats the benefits of jQM's ajax loading since you're loading all your HTML at the start (unless your site is small)

你肯定想使用ajax加载，jQM只在你的<div data-role="page">中拉入代码但这会使你的JS复杂化，见下文

You definitely want to use ajax loading, jQM only pulls in the code in your <div data-role="page"> BUT this complicates your JS see below

你不需要多个 JS 文件，但你需要在开始时加载所有的 JS，我们通过做两件事来完成这个:1.我们把一个 on 侦听器在文档根目录，并侦听 pageinit/pageshow 事件.每次加载页面时，这些都会被触发，您还可以方便地引用当前页面，并且您可以使用页面上的 attr 来确定它是哪个页面.2. 将所有 JS 包含在某种类型的包含中(希望您使用的是 PHP、CF 或其他东西)并将其放在每个页面上，无论用户浏览您的移动设备的哪个入口点网站，他们会加载所有代码

You don't need multiple JS files, BUT you do need to load all your JS at the start, we accomplish this by doing two things: 1. we put an on listener at the document root, and listen for pageinit/pageshow events. Everytime a page is loaded these are triggered, you also have a handy reference to the current page, and you can use an attr on the page to determine what page it was. 2. Have all the JS in an include of some sort (hopefully you are using PHP, CF or something) and put this on every page, that way no matter which entry point a user browses to your mobile site with, they get all the code loaded

缺点是最初加载了所有 JS，但缩小后我们发现这没什么大不了的，如果真的很担心，请查看 RequireJS - 而且它使调试变得轻而易举，因为 JS 就在那里，我们可以轻松地使用调试器并放置断点.如果你在每个页面上动态加载 JS，你会增加你需要在每个页面转换上返回的数据，你会变得丑陋，因为你重新加载了多余的 JS，并且很难调试动态 JS.

The downside is that all the JS is loaded initially, but minified we find it's no big deal, and if it's really a concern look into RequireJS - plus it makes debugging a breeze since the JS is all there we can easily use the debugger and place breakpoints. If you load JS dynamically on each page you increase the data you need to return on each page transistion and you have ugliness because you reload redundant JS and it's hard to debug dynamic JS.