Upgraded ember to v1.3.1 and changed deprecated properties...
Using ember-data for the model to make sure this doesn't cause
problems..
Switched to using the {{input}} for plain text fields and custom
components for the subclasses...
Using the default model name for the model and an ObjectController as per
the ember getting started guides...
fixed handling of falsy values in required rule
Hacky fix to allow ValidatorViewSupport views to access the validator
hosted by an ObjectController.

I'm not sure if this approach is correct but it seems to make the example
work...
Merge branch 'feature/example-with-ember-data' of https://github.com/vitch/ember-validation
upgraded dependencies
added check for ObjectController
Introducing a property which only needs to be validated based on the
status of another property.

When a user isNinja then they need to input the "secret ninja word"
which should be "NINJA!". Fields to toggle the isNinja status and
enter the secret word are now available on example 2.

This seems to work OK but breaks if you do the following:

 * Load the demo and navigate to example 2
 * Check "isNinja"
 * Enter something in the "secret ninja word" box then delete it
 * Uncheck "isNinja"
 * Click "Validate"

You will see the error message for "secret ninja word is required" is
shown even though the word shouldn't be required when isNinja is false.
Allowing the `required` rule to take a parameter.

This parameter (`isRequired`) can be a boolean or a function. If it is
a boolean then if it is true the field is required and if it is false it
isn't. If a function is passed then this function is called every
time the field is validated and should return a boolean (true if the
field is required, false if it isn't).

As you can see from the code in the previous commits, I incorrectly
assumed this was the original behaviour of the rule. Now my "Secret
Ninja Word" seems to validate as I would expect.

There is still a bit of weirdness because of the `wasFocused` property
on the textfield (if you show and hide the text field it stops
validating on change even when you might expect it to) but I am OK with
that for now.
Using `Ember.isEmpty` rather than a custom `isEmpty` method.

I was running into problems with the required rule not being applied
when a model was validated before you had visited all of the fields.

These turned out to be because of undefined values. `Ember.isEmpty`
catches `undefined` as well as `null` and `''` (and also an empty
array but I think that's OK?)
Added some new tests testing the "required rule with function param"
Merge pull request #7 from vitch/feature/is-empty

Using `Ember.isEmpty` rather than a custom `isEmpty` method.
Should support specifying a base class without explicitly declaring a validator property

Example:
App.Form = Em.Object.extend(Ember.Validation.ValidatorSupport);
App.Form.create();
Merge pull request #8 from narkeeso/fix-null-validator-createResult

Should support specifying a base class with ValidatorSupport mixin
Merge branch 'feature-request/if-rules'
Not ignoring the dist directory.

I don't necessarily approve of including generated assets in a repo
but in this case I need to be able to install my modifications via
bower and the upstream repo seems to be abandoned so this is the
quickest/ easiest way I can use my changes in my program...