Book Image

Mastering jQuery

By : Alex Libby
Book Image

Mastering jQuery

By: Alex Libby

Overview of this book

<p>Mastering jQuery has been written not only to help maximize your skills with core functionality in the library, but also to explore some of the more intriguing ways of using the library to achieve real-world solutions that could feature on any website or online environment.</p> <p>You'll start with a look at some of the more advanced ways to incorporate the library into your pages, followed by working with forms and advanced form validation using regular expressions. Next you'll move on to animating in jQuery, advanced event handling, and using jQuery effects.</p> <p>Finally, you will develop practical examples of using jQuery with external functionality such as node-webkit, before finishing with a session on optimizing your version of the library for maximum efficiency and exploring best practices for using QUnit.</p>
Table of Contents (21 chapters)
Mastering jQuery
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Understanding why performance is critical


Picture the scene if you will – your team has created a killer web-based application using the latest techniques, which does everything under the sun, and you're ready to sit back and enjoy the laurels of your success. Except for one small but rather critical thing…

No one is buying. Not one copy of your application is being sold – the reason why? Simple – it's really slow and hasn't been properly optimized. No amount of selling will get over the fact that in this age of mobile devices, a slow application will turn off the users.

Should we be concerned with the performance of our application? Absolutely! There are good reasons for being critical of our application's performance; let's take a look at a few:

  • The advent of mobile devices with the associated costs of surfing means that our content must be optimized to ensure the site displays quickly, before the connection times out

  • It's all too easy to focus on development instead of fixing cross-browser...