Index Page.... simple, no nonsense. Also -- Boring

I had some idea of what was going on since I built a small .mobi site for this company last year geared toward the iPhone/iPod Touch. It turned out OK, but was nothing I really felt stood out. It works, but I honestly don’t think it gets much attention. I’d like to revisit it sometime and make some improvements with what I’ve learned on this project.

Date and Nights Selection

The site will not be available outside of this office, but I’ve got some screenshots AND A VIDEO showing off the functionality. I’m not much of a designer, so it’s not as pretty as it could be probably, but it works I think. I’ll post a couple of the fun jQuery stuff I found/did as well. I think the most instructional and entertaining part was modifying the jQuery quicksearch plugin from www.rikrikrik.com to be able to use an on-screen keyboard.

And somehow I don’t have a screenshot of that…will update later

Rather than creating a separate keyboard and try to tie it into the event handling for quicksearch, I ended up extending the plugin, adding new functionality through the options passed during the .quicksearch() call so the keyboard was fully integrated. It took some trial and error, and it likely could be done “better”, but it works, and functions great.

$('table#cabin_names tbody tr').quicksearch({
				position:'after',
				attached:'#uber_wrap',
				labelText:'',
				inputClass:'sel wide',
				watchElement:'li.alpha_btns',
				keyboard: true,
				keyboardId: 'alpha_btns'
			});

The ‘watchElement’ option is the elements that should trigger the qs() function in quicksearch. ‘keyboard’ defaults to false, but when set to true, it renders the html to insert the keyboard and bind the events to do the proper stuff. ‘keyboardId’ just lets you define the element Id so you can style at will. This extension of the plugin likely has no real use beyond sites designed for touch screens, but it was still educational, and was an interesting introduction to plugins in jQuery. I’ve never written my own, but if I find some functionality I need in the future, maybe I can break into that field too.

# of Guests

Anyhow, there’s not much else to say. This site was designed specifically for this screen, specifically to run in Firefox, specifically in Fullscreen mode. If I had more time I think it could be made to be a bit more flexible, but I suck at CSS, and I just didn’t know how to make a few things flow fluidly on different sized screens. Enjoy!

kiosk_demo

List of cabins available for selected dates and # of guests

One of the other really fun things to write/integrate was the scrolling buttons. I realized after the initial design that having regular scrollbars just wouldn’t be usable with a touch screen interface. Theoretically I could have altered the Firefox userContent.css to enlarge the scroll bars to the point they would have been usable, but that just didn’t feel right. Once again, though, jQuery plugins to the rescue! I found a nice little scrolling plugin that allowed me to bind relative scroll positions with easing to click events on the fixed-position nav-box on the right side. Not sure I’m thrilled with how it looks right now, but at least it’s functionally complete. Can always tweak it down the road.

Fun screen to write. "Buttons" are actually labels for hidden checkboxes. jQuery styling changes make it look fancy

Individual cabin page...small photos are clickable to rotate through pictures

First off, there is the the combined magic of the jquery Form plugin from malsup.com which creates a nice AJAX-submitted form with one quick line of code

$('#form').ajaxForm();

Optionally, you can pass the .ajaxForm() function any options that you would normally pass to a regular jQuery .ajax() method like so….

Now that’s fun, but it can be extended just a LITTLE bit more with the jquery validate plugin. Here we can define some simple rules in JSON format and the validation plugin will automatically display customizable messages for any errors that are found before submitting the form. The validation function takes the option submitHandler to create the ajaxSubmit event from the Form plugin above.

Here is an example:

$('#contactus_form').validate({
	submitHandler: function(form){
		$(form).ajaxSubmit({
			success: function(msg){
				alert(msg);
			},
			error: function(msg){
				alert(msg);
			}
		});
	},
	rules:{
		name:"required",
		email:{
			required:true,
			email:true
		},
		message:"required"
	},
	messages: {
		name:"Name is required",
		email:{
			required:"Email is required",
			email: "Email is in an invalid format"
		},
		message:"Some message to the staff is required"
	},
	errorLabelContainer:"#ajaxmsg",
	wrapper:"li"
});

Obviously you need to validate the data in whatever script you are handling on the server side, but the jQuery error messages are a great way to improve your forms usability and they can be styled to be attractive and make any input errors very clear to your users.