Add a pod spec, copied from https://github.com/CocoaPods/Specs/blob/master/TITokenField/0.9.0/TITokenField.podspec
Update pod spec to point to TribeHR repo.
Update pod spec to exclude files that are part of the example, not the library itself
Merge pull request #1 from sadlerjw/podspec

Podspec
Allow the user to specify whether the TITokenFieldView should be scrollable.

If the user allows scrolling, we still disable scrolling internally while the results table
is showing - if the user allows scrolling (which is the default value) then there should
be *no change in behaviour* in this commit.

If the user disallows scrolling, then the entire view should *never* be scrollable. This
introduces the ability to specify add a scrollview to the contentView, meaning that the
To: box always appears on screen, and doesn't scroll away with the content, as is the
current behaviour.
Merge pull request #3 from sadlerjw/allow-scroll-disable

Allow the user to specify whether the TITokenFieldView should be scrollable
Put layout-related code in layoutSubviews instead of setFrame

When the view is part of an autolayouted view hierarchy and its size is updated
via a change in constraints, setFrame is not called, but layoutSubviews is. So to
properly support autolayout, we need to do these calculations as part of layoutSubviews.
Fix calculations for _contentView's height

The content view's height depends on _tokenField's frame, therefore we have to
calculate _tokenField's frame first.
Don't call layoutSubviews directly; always use setNeedsLayout instead.
Allow TITokenFieldView to manage the frame of its own content view.

This enables the use case where the TITokenField is pinned to the top of the screen
and then contents of contentView are allowed to scroll independently. Usually if
managesContentViewFrame is set to YES, you'll also want to set scrollEnabled
on the TITokenFieldView to NO.
Merge pull request #2 from sadlerjw/autolayout-fixes

Autolayout fixes
Allow read-only access to the results array

This enables the scenario where the delegate can substitute the top-most result
for the token about to be added. This is a basic level of auto-completion.
Merge pull request #4 from sadlerjw/read-results-array

Allow read-only access to the results array
Allow custom search comparison options, for example to do diacritic-insensitive searches.
Merge pull request #5 from sadlerjw/custom-search-options

Allow custom search comparison options, for example to do diacritic-insensitive searches.
Fix the issue where the non-trimming of Zero Width Space UC character would prevent the correct filtering of the source array

DELIVERS https://www.pivotaltracker.com/story/show/53980813
Merge pull request #8 from carranca/give-kudos-names-bug

Fix the issue where the non-trimming of Zero Width Space UC character would prevent the correct filtering of the source array
Make sure that the cursor and text appear in the correct position on iOS 7

It appears that the default contentVerticalAlignment was "top" in iOS 6 and earlier,
and "centre" in iOS 7, so we just explicitly set it to "top" since that's what the layout
code in TITokenField expects it to be.
When typing in the token field on iOS 7, the field would disappear behind the nav bar.

This is because the content insets were modified by the system to account for the transparent nav
bar (top inset = 64) but the contentOffset-changing code in setResultsModeEnabled:animated: assumed
that all changes would be relative to top inset = 0.

We can fix this simply by including the contentInsets.top in the calculation of the contentOffset's Y value.
Merge pull request #9 from sadlerjw/fix-text-align-ios-7

Make sure that the cursor and text appear in the correct position on iOS 7