Importing Agent theme from Collin Allen

I also changed the license to MIT with his blessing.  Here's a slightly censored email:

Subject: Re: Agent theme for Uniform
References: <CAPf=UYYYcY-zM9Q4sEZuNVvQ3WSUd1vvqnB0GF2q3TDBWxf0fg@mail.gmail.com>
From: Collin Allen <collin@comma******.com>
In-Reply-To: <CAPf=UYYYcY-zM9Q4sEZuNVvQ3WSUd1vvqnB0GF2q3TDBWxf0fg@mail.gmail.com>
Message-Id: <DCC10F96-6FE2-4506-8568-11B5F075DD1E@comma******.com>
Date: Fri, 12 Oct 2012 08:41:38 -0700
To: Tyler Akins <******@gmail.com>

Hi Tyler,

I think, at the time, I just used the same license as the other Uniform themes, but I could be mistaken. In any, event, though, feel free to relicense it under MIT :) Not a big deal!

Where will this new repository be hosted at?

Thanks!

~ Collin

Sent from my iPad

On Oct 12, 2012, at 6:34 AM, Tyler Akins <******@gmail.com> wrote:

> I would like to include your agent theme in Uniform's repository.  I'm adding support for many other form fields and would like to "hit the ground running" when the next version is released by having more than one theme available for users.  You license the agent theme as creative commons share-alike, which is not the same as Uniform's MIT licensing.  I don't want to have license conflicts by including your theme under a different license.  So, I was hoping that you'd be ok with me relicensing the agent theme under MIT and including it in Uniform's repository.
>
> What are your thoughts?
>
> --
> Tyler Akins
Skip generated files
Moving themes into css/ directory for easier use on website
Omitted these from the last commit - moving to css/ folder
Moving to css folder and fixing/updating styles a bit
Updating upgrade instructions for changed sprite
Removing minified version and allow changing theme
Moving to bin/ directory
Count words in minified version for better compression
Bumping version to 2.0.0
Updating noSelect
Removing strings for better minification
Adding new option - eventNamespace
Cleanup, expose functions off main jQuery object
Updating to match library
Adding in website files and build scripts

Putting the website in the development branch with a build script so we can update themes, test them with the debug page, see how the site would render, then just build a tarball and update the gh-pages branch with the changes.  This also removes duplicate documentation for the options and helps to keep things up to date.
Adding code from issue #104

Older versions of Firefox don't send click events or follow links properly.  This code is provided in the bug report to fix this issue.
jQuery prefers us to use .prop() if available
Adding documentation
Update button text on $.uniform.update()

This is to address issue #131