jQueryMobile 1.1.0 and MVC4


I’ve been working on a project recently targeting mobile devices and have been using the latest version of jQueryMobile, 1.1.0 (Release Candidate 1 as of Feb 28, 2012 - http://jquerymobile.com/blog/2012/02/28/announcing-jquery-mobile-1-1-0-rc1/). This new version offers a number of enhancements on the jQueryMobile front (and introduces a few new issues, which will hopefully be worked out before being released as production). The great thing about advances in jQueryMobile is that it ties directly in to Microsoft’s plans for MVC 4 (also currently in Beta as of September, 2011) and their new mobile project template (see http://www.asp.net/whitepapers/mvc4-release-notes#_Toc317096197). My next few blog posts will examine jQueryMobile 1.1.0 and how we can leverage some of the tools in our own MVC-based, mobile-targeted applications.

Getting Started

In getting started with jQueryMobile (“JQM”) 1.1.0, the first thing to note is that it now supports jQuery version 1.7.1 (the previous version of JQM ONLY supports jQuery 1.6.4). Some significant enhancements include improved slider (including a “step” attribute to make sliding easier) and flip switches (fixed the awkwardness of the 1.0 version), the inclusion of a “mini” version of form elements, two new transitions, a navigation search (filter) capability, and a nice AJAX loader design and options, in addition to bug fixes and other enhancements. There is even an enhancement that will allow JQM to play nicely with 3rd party controls (which obviously is of interest to us using Infragistics’ jQuery tools (http://www.infragistics.com/dotnet/netadvantage/jquery-controls.aspx#Overview)!).

This version of JQM solved a host of issues I had previously (ie, the checkbox control!) and lays the foundation for additional items to be included in the future, both from the JQM team, plugin developers, and other 3rd party control suppliers. Still lurking in the shadows is Android sluggishness, so I’m hoping that the brain trust collaborates on ways to quicken it on Android.

The Plan

Over the next few blog posts, I will introduce and evaluate the various elements in JQM that are more popular to us as mobile device developers using a development platform. For instance, pages for us are in theory irrelevant since we will be using views. However, touch and form elements are indeed of interest. If popular demand dictates, however, that specific items be addressed, we can certainly spend a blog post or two on those things.

What’s Next?

Well, let’s start individually by downloading the aforementioned pre-release versions of jQueryMobile and MVC4, install them, and start exploring in preparation of our short series. Until then, happy coding…