Update assets to jQuery-File-Upload 9.8.0

[opti]

This PR includes:

• updated assets from jQuery-File-Upload v9.8.0
• moved vendor/assets to app/assets for Rails 4 compatibility
• couple more helpers for easy include basic-plus, angularjs or jquery-ui versions
• updated README.md

[ipd]

@opti I noticed your PR sitting here. So, is this gem currently unmaintained? Perhaps @tors has moved on or is too busy?

I'd like to use the gem, but am running Rails 4.1.x and am wondering what to do. Perhaps i should just use your fork?

thanks!

[opti]

@ipd yeah, the origin gem looks unmaintained for a while and I'm not sure it will be back on track. Anyway, I'm using my fork exactly with Rails 4.1.x. Didn't noticed any issues yet.

[ipd]

@opti ok, thanks for getting back to me.

[tors]

@opti Hola! Thanks for this! I've been very busy at work. I've added you as a collaborator.

[ipd]

Thanks @tors !

We should probably version the gem so that people who are on rails < 4.x will be able to continue to use the old version.

Also, we should create a new example app for Rails 4.x.

[opti]

Thanks for merging this @tors

[opti]

hey @tors I've created a release tag v0.4.2, if you don't mind you can push it to rubygems

[tors]

@opti roger that! Thanks!

[felixbuenemann]

You should probably add back the X-Requested-WIth Patch for the Iframe-Transport Middleware before making a new release, see commit d246fe6 for details.

[opti]

@felixbuenemann I'm not sure that this is a good idea to make those changes in that repo. This js file is copied from original repo. Making fixes here forces repo maintainers to always keep in mind this fix on every future assets upgrade.
Maybe it make sense to open a pull request with this fix to the @blueimp's original jQuery-File-Upload repo.

[felixbuenemann]

Jepp, that's what I though and it was rejected, see blueimp/jQuery-File-Upload#3291. The problem is that this repo used to have this patch, so not having it brakes the usage of the iframe transport middleware.

Maybe the middleware could be changed to somehow detect the request without the extra header.

[opti]

@felixbuenemann I see. You're feel free to add it back while there is no another solution yet.

[felixbuenemann]

I think the best solution is to remove the middleware, see #69 for reasons.