jQuery Mobile Up and Running 原版英文PDF

需积分: 10 108 浏览量更新于2024-07-19 收藏 20.96MB PDF 举报

"jQuery Mobile Up and Running 无水印原版pdf" 《jQuery Mobile Up and Running》是由Maximiliano Firtman编写的英文书籍，旨在帮助读者快速掌握使用jQuery Mobile进行移动应用开发的技能。这本书详细介绍了如何利用jQuery Mobile这个强大的前端框架构建响应式和触摸友好的移动Web应用。jQuery Mobile是jQuery项目的分支，专门针对移动设备优化，它提供了丰富的组件、易于使用的API以及一套统一的事件处理机制，使得开发者能够快速创建跨平台的移动应用。在本书中，作者Maximiliano Firtman将带领读者深入理解jQuery Mobile的核心概念，包括： 1. **基础设置**：讲解如何引入jQuery Mobile库，配置HTML结构以适应移动设备，以及如何利用数据属性(data-attributes)和CSS类来定制样式。 2. **页面结构**：介绍jQuery Mobile中的“页面”概念，如何组织和链接多页应用，以及如何实现页面过渡效果。 3. **交互元素**：详述各种交互元素，如按钮(buttons)、表单(forms)、列表(listviews)、可折叠内容(collapsible content)和网格(grid)等，以及如何与它们进行交互。 4. **导航和路由**：讨论在jQuery Mobile中处理页面导航的方法，包括无刷新导航和历史管理，以及如何使用hashchange事件来实现应用程序的路由。 5. **触摸事件和手势**：介绍如何处理触摸事件，如tap、swipe、drag等，以创建更自然的移动用户体验。 6. **性能优化**：讨论移动Web应用的性能问题，提供优化策略，如延迟脚本加载、减少HTTP请求、压缩资源等。 7. **主题和自定义样式**：解释如何使用jQuery Mobile内置的主题系统，以及如何通过Sass（Syntactically Awesome Style Sheets）来自定义界面样式。 8. **集成和扩展**：介绍如何与其他JavaScript库和框架（如AngularJS）结合使用，以及如何编写自定义插件来扩展jQuery Mobile的功能。 9. **测试和调试**：提供关于在不同移动设备和浏览器上测试应用的建议，以及如何使用开发者工具进行调试。 10. **部署和发布**：讨论将应用部署到不同的平台，如iOS的Safari、Android的WebView，以及如何打包成Web应用或混合应用（如PhoneGap）。本书适合有一定jQuery基础，希望通过移动Web技术进行开发的开发者阅读。无论你是初学者还是有经验的开发者，都能从中获得关于jQuery Mobile的宝贵知识，从而提升你的移动开发能力。请注意，该资源为无水印的原版pdf，可在多个PDF阅读器上正常打开。如果发现任何版权问题，应联系上传者或相关平台进行处理。此外，你可以在美国亚马逊官网上查找更多关于此书的详细信息。

So, yes…it’s the same Web. However, when developing for the mobile web we are

targeting very, very different devices. The most obvious difference is the screen size,

and yes, that will be our first problem. But there are many other not-so-obvious dif-

ferences. One issue is that the contexts in which we use our mobile devices are often

extremely different from where and how we use our comfortable desktops or even our

laptops and netbooks.

Don’t get me wrong—this doesn’t mean that, as developers, we need to create two,

three, or dozens of versions duplicating our work. This is where jQuery Mobile comes

to the rescue.

You don’t need to do anything special when designing for the mobile web

Almost every smartphone on the market today—for example, the iPhone and Android-

based devices—can read and display full desktop websites. Yes, this is true. Users want

the same experience on the mobile web as they have on their desktops. Yes, this is also

true. Some statistics even indicate that users tend to choose web versions over mobile

versions when using a smartphone. However, is this because we really love zooming in

and out, scrolling and crawling around for the information we want, or is it because

the mobile versions are really awful and don’t offer the right user experience? I’ve seen

a lot of mobile sites consisting of nothing but a logo and a couple of text links. My

smartphone wants more!

One website should work for all devices (desktop, mobile, TV, etc.)

As we will see, there are techniques that allow us to create only one file but still provide

different experiences on a variety of devices, including desktop, mobile, TV, and game

consoles. This vision is called “One Web.” Today, there are a lot of mobile devices with

very low connection speeds and limited resources—non-smartphones—that, in theory,

can read and parse any file, but will not provide the best user experience and will have

compatibility and performance problems if we deliver the same document we would

for the desktop. Therefore, One Web remains a goal for the future. A little additional

work is still required to provide the right user experience for each mobile device, but

there are techniques that can be applied to reduce the work required and avoid code

and data duplication.

Just create an HTML file with a width of 240 pixels, and you have a mobile website

This is the other fast-food way to think about the mobile web. Today, there are more

than 3,000 mobile devices on the market, with almost 50 different browsers (actually,

more than 500 different browsers if we separate them by version number). Creating

one HTML file as your mobile website will be a very unsuccessful project. In addition,

doing so contributes to the belief that the mobile web is not useful.

2 | Chapter 1: The Mobile Platform

Mobile Webapps

I’m not going to enter the discussion about mobile web development versus native

development. In fact, I believe that the discussion is mostly wrong. Often the discussion

is about native code versus JavaScript code or browser apps versus installed apps.

However, what these discussions fail to mention is that multiplatform development is

quite a challenge in the native development environment because each platform re-

quires a different SDK. Therefore, because the real concerns are ease of development

and deployment to multiple mobile devices, mobile web development is a perfect sol-

ution for most situations. The term webapp has plenty of synonymous or similar con-

cepts, such as mobile webapps, widgets, hybrids, HTML5 apps, and more.

In particular, a mobile webapp differs from typical mobile websites in its purpose. A

webapp typically has a more transactional way of thinking in the user interface, emu-

lating native mobile applications. It is still created using web technologies (HTML, CSS,

JavaScript, AJAX) but offers an application-similar experience to the user.

Frequently mobile webapps also make use of HTML5 features, such as offline or geo-

location access, to provide a better experience. Geolocation is not an official part of the

HTML5 specification, but a W3C API of its own; however, it is often mentioned under

the HTML5 umbrella.

A webapp can be implemented in many ways (as shown in Figure 1-1) including:

• Accessed from the browser

• Installed as a full-screen webapp

• As an installed webapp via a package officially implemented by vendors (sometimes

called widgets)

• As an installed webapp embedded in a native application, commonly known as

hybrid

We will cover how to create these webapps in the rest of the book. For more in-depth

information, just cross the street to my other book: Programming the Mobile Web

(O’Reilly).

A webapp typically generates new challenges for web designers and developers, such

as loading views instead of pages, maintaining a two-way navigation between views,

and creating rich controls specifically for touch devices.

So, Again…Why Do We Need jQuery Mobile?

If you read the last few pages (and I’m pretty confident you did), you are aware that

mobile web design and development presents new challenges for us. We need to create

webapps that are more than simple websites; there are too many devices out there with

different browser compatibilities; and there are also too many libraries trying to solve

the same problem with mixed community and device support.

Why Do We Need jQuery Mobile? | 3

What jQuery Mobile Is Not

To understand jQuery Mobile, it is very important to know what it is not.

jQuery Mobile is not a jQuery alternative for mobile browsers.

To use jQuery Mobile, you need to include the typical jQuery framework. It is not

a replacement; it is a UI layer on top of jQuery.

jQuery Mobile is not a webapp SDK.

You can create the whole mobile experience with jQuery Mobile but you will need

some additional work to compile it as native apps. We will see how, why, and when

to do this in the next chapters.

jQuery Mobile is not a framework for JavaScript lovers.

Except in the case of certain advanced topics, you won’t need any JavaScript code

for jQuery Mobile to work. That is great if you are a web designer who hates all of

those braces and semicolons.

jQuery Mobile is not the solution for all mobile applications, websites, or games.

However, it covers solutions for most of them. For the others, well…I have to con-

vince you to read my other book somehow.

The Framework

If you don’t know what jQuery is, you may be a time traveler from 10 years in the past.

If you are Marty McFly, point your browser to http://jquery.com and read about this

incredibly useful JavaScript framework, the most used one on the Web since 2007.

jQuery Mobile is a framework that delivers webapp experiences to mobile and tablet

devices, mainly with touch interfaces, effortlessly, across multiple platforms, and using

only HTML5 standard code. A jQuery Mobile app looks like Figure 1-2.

The platform uses the jQuery “core” framework, a JavaScript library, a CSS 3 stylesheet,

and some resource images.

jQuery Mobile is comparable to jQuery UI on the desktop side: it’s just a UI framework.

The name (without any UI inside) leaves you to wonder whether it’s a core framework;

but I believe the decision was made to take advantage of the power of the jQuery

trademark inside the designer and developer world.

The framework was created by the same team as the main jQuery frame-

work, whose leader is John Resig, JavaScript Tool developer for the

Mozilla Corporation (@jeresig on Twitter).

This new platform, like jQuery and jQuery UI, was released as an open source project

under a dual license MIT or GPL version 2.

What Is jQuery Mobile? | 5

剩余269页未读，继续阅读

yinkaisheng-nj

粉丝: 763
资源: 6231

jQuery Mobile Up and Running 原版英文PDF

Master Mobile Web Apps with jQuery Mobile(3rd) 无水印原版pdf

jQuery Mobile Up and Running

jQuery Mobile Cookbook 无水印原版pdf

10个jQuery Mobile演示网站示例

h5 jquery mobile模板

jquery mobile社区页面代码

jquery mobile 个人网站

jquery mobile 开发app

jquery mobile个人网站

jquery mobile app案例

最新资源