Caution: I don’t recommend trying this in a production environment. The branch of jQuery UI I’m using in this series is not considered stable and is not meant for prod releases. You can, however, learn about the new features in the UI library and stretch your development capabilities!
jQuery UI continues to impress. The development team’s commitment to extensibility means that their own widgets are up for review at each release, and even at each milestone of a release. The great thing about the modularity in jQuery UI is that you can build your own widgets or customize the existing ones with the very parts used to build the core set in the first place.
But, before you even have to venture in that direction, you already have the ability to work with the many themes (or roll your own!) to make it look and feel the way you want to.
Focusing on stability and flexibility in the 1.9 build, here are some of the important bits that will be surfacing in this release of jQuery UI:
- Improved, tested code in many of the existing widgets
- Much better accessibility accross the suite (for disabled users/browsers)
- Revisited the API design on a number of widgets (Button, Dialog, Position, ProgressBar, Slider, Tabs)
- Improved collision detection on Position and added a new flipfit mode
- A new version of Theme Roller, the download builder and the web site
- New widgets: Tooltip, Spinner, Menu and Menubar
Here’s the descriptions of the new Widgets from the horse’s mouth:
- Tooltip: A tooltip is a small overlay that sits over the main page that can be used to provide content or functionality that does not need to be always visible.
- Spinner: A spinner (stepper) is a simple widget that allows users to increment or decrement the current text box value without having to input it manually.
- Menu: Menu transform a list of anchors into a widget with mouse and keyboard support for selecting an item.
- Menubar: A horizontal menu with nested vertical flyout menus for each menu item.
While I’m a huge fan of the integrated package manager in VS2010, you’re not going to find these bits on Nuget. You’re going to either need to follow the links from the Milestone 6 post or grab the bits directly from googlecode.com.
Once you grab the zip, unpack it and have a look at the contents.
Pretty much everything we’re going to need will be in the UI and Themes directories. If you’re not familiar with jQuery UI, the Themes directory is where all the CSS is stored for making the entire UI has a consistant look-and-feel. UI is where all the code exists for all components.
You have the choice of building up your own set of functionality for the widgets you’re using by including the smaller UI libraries, or you can fire up the full kit with one library. This allows the bandwidth-concerned developer the opportunity to choose lighter weight code files (or even compile only the needed scripts into a minified script of their own creation).
As an example, if you wanted to make use of the new spinner, you’d need to include:
Of course, you would also need to include the relevant CSS files, but with a total weight of 7Kb (and the option to use multiple CDNs out on the web) you might as well just include the full jQuery-ui.css.
I’m going to assume you’ve done a little MVC work before, if not, hold tight for the walkthrough after the bullet list. I’m using version 3 of the MVC Framework in Visual Studio 2010 SP1.
Here’s the steps:
- Create a new MVC 3 project using the “Empty” template
- Delete the “themes” folder in Content
- Update jQuery with NuGet
- Add jQuery UI 1.9 files to the project (“themes” go in Content and “UI” go in Scripts)
- Add a HomeController
- Add an Index view for HomeController
- Modify the _Layout.cshtml file (your master page) to include jQuery UI and the theme CSS
Here’s the visual play-by-play of that in action.
Open up Visual Studio 2010 and select File –> New Project. Create a new ASP.NET MVC 3 Application.
Name the project and click OK. Finally, select the “Empty” template from the list and click okay.
Navigate to the content folder at the root of the project and delete it.
Next, we need to get the latest version of jQuery so that jQuery UI 1.9 is happy with us. Go to the Package Manager Console and type:
…and you’ll see the following:
NuGet (the heart of this console) happily goes off and updates all our dependencies for us.
Pop over to that zip folder you downloaded. You’ll need to make sure you’ve extracted all the files. Copy the themes directory, then switch over to VS2010 and paste it into the content folder. Do the same with UI, but paste it as a sub folder into Scripts.
We’re going to use the tooling in MVC 3 to do the next bit of work for us, in particular, the code generation that creates controllers and views for us. Right-click on the Controller folder, then select Add –> Controller. Call it HomeController when the dialog prompts you (this is so that we can take advantage of the default routing rules in MVC).
Your HomeController class is automatically generated with the Index action created for you. Right click on the name of this action and select Add View. Accept the default name (it picks Index for you because that’s the action you right-clicked).
Almost there! All that’s left to do is to adjust our Layout. The _Layout.cshtml file is like a MasterPage from our days of WebForms and we use it to inject our head element containing the script and CSS references.
There’s already a jQuery reference there, so that needs to be update to the correct version (1.6.4 as at the time of this writing). You’ll need to add the jquery-ui.css and jquery-ui.js files as well.
For you copy-and-pasters out there:
And that’s it! You’re all set up to use jQuery UI 1.9.
Things are a little drawn out right now because we can’t grab the preview bits on NuGet.
Keep in mind that once the updated library is released, you will simply be able to update jQuery UI through the package manager console in Visual Studio 2010. This, in turn, will resolve and update all other dependancies and will also incorporate the vsdoc files needed for IntelliSense.
Right now we really only have the guts in place to make jQuery UI tick, but it’s always good to stay on top of your game. Get your hands dirty now!
1) Download the jQuery UI 1.9 development branch (Milestone 6 post)
2) Create an ASP.NET MVC 3 project
3) Get jQuery UI 1.9 in your project and start exploring
4) Try jQuery UI 1.9 in a copy of one of your current project and see if anything breaks
Now that you’ve got the library in your project, we’re going to have look at some of the controls in more detail. One of the great things in MVC is the insanely simple rendering of templates and data binding, especially when coupled with something like Entity Framework.
Hold on to your hats, in the next segment we’re going to use data annotation attributes to wire up a jQuery UI Spinner widget.