3 ms·

> Depends on the size of your Gemfile. Really, it's not large. The things I'm most worried about are gem 'carrierwave' gem 'jquery-fileupload-rails' ge

> Depends on the size of your Gemfile. Really, it's not large. The things I'm most worried about are gem 'carrierwave' gem 'jquery-fileupload-rails' gem 'jquery-datatables-rails' gem 'jquery-ui-rails' All of those 1. I don't understand their guts too well, and 2. if they fail then our target audience will hate us and hunt us down with pitchforks.

davidw 13y ago
As an aside, how is the jquery-fileupload thing? I was reading about it, and when I saw there was some weird iframe thing for IE... I closed the page and walked away. That kind of thing looks like it could be a nightmare if something goes wrong.
- jpdoctor 13y ago
  > As an aside, how is the jquery-fileupload thing? I don't have a good answer: Fine to program with, but certainly took some doing for our particular need. (We had a number of requirements that made the "easy" out-of-the-box jquery-fileupload not suitable.) Ask me in a couple of months and I'll probably have a lot of opinions to give. > and when I saw there was some weird iframe thing for IE... I closed the page and walked away. We are migrating customers from a C++ desktop app to a web interface: So anyone on old IE with problems will be informed that they're not supported on the new system, so keep using the old and let us know after they upgrade. :) (Newer IE is OK.) Deviously, this also prevents absolutely everyone from ditching the old app and swamping the new system on day 1.
- ebiester 13y ago
  Unfortunately, that's the necessary hack, as far as I know, if you want to have an ajax submission.
- fbuilesv 13y ago
  Having recently worked with this project I can say that it's pretty reliable and way better than most jQuery plugins you'll find out there. The iframe transport method for uploads is useful for browsers that don't support XHR file uploads (basically IE < 10). You can read more a bit about how it works in: https://github.com/blueimp/jQuery-File-Upload/wiki/Frequently-Asked-Questions#why-is-the-file-input-field-cloned-and-replaced-after-each-selection https://github.com/blueimp/jQuery-File-Upload/wiki/Frequentl... or directly in the source: https://github.com/blueimp/jQuery-File-Upload/blob/master/js/jquery.iframe-transport.js https://github.com/blueimp/jQuery-File-Upload/blob/master/js... (it's pretty small).
sc00ter 13y ago
CarrierWave appears to support Rails 4; the rest are not doing anything special other than making jquery js acripts available in the asset pipline without manually installing them, so shouldn't cause any issues. You'll have a bit of work to do to migrate to strong parameters, but you can always add the protected_attributes gem back to re-enable support for attr_accessible. I'd suggest checking out the Rails 4 migration RailsCast.
- aaronbrethorst 13y ago
  I've been using Carrierwave with Rails 4 RCs and haven't run into any trouble with it.
  - jpdoctor 13y ago
    Thank you for this info.

davidw 13y ago

As an aside, how is the jquery-fileupload thing? I was reading about it, and when I saw there was some weird iframe thing for IE... I closed the page and walked away. That kind of thing looks like it could be a nightmare if something goes wrong.

jpdoctor 13y ago
> As an aside, how is the jquery-fileupload thing? I don't have a good answer: Fine to program with, but certainly took some doing for our particular need. (We had a number of requirements that made the "easy" out-of-the-box jquery-fileupload not suitable.) Ask me in a couple of months and I'll probably have a lot of opinions to give. > and when I saw there was some weird iframe thing for IE... I closed the page and walked away. We are migrating customers from a C++ desktop app to a web interface: So anyone on old IE with problems will be informed that they're not supported on the new system, so keep using the old and let us know after they upgrade. :) (Newer IE is OK.) Deviously, this also prevents absolutely everyone from ditching the old app and swamping the new system on day 1.
ebiester 13y ago
Unfortunately, that's the necessary hack, as far as I know, if you want to have an ajax submission.
fbuilesv 13y ago
Having recently worked with this project I can say that it's pretty reliable and way better than most jQuery plugins you'll find out there. The iframe transport method for uploads is useful for browsers that don't support XHR file uploads (basically IE < 10). You can read more a bit about how it works in: https://github.com/blueimp/jQuery-File-Upload/wiki/Frequently-Asked-Questions#why-is-the-file-input-field-cloned-and-replaced-after-each-selection https://github.com/blueimp/jQuery-File-Upload/wiki/Frequentl... or directly in the source: https://github.com/blueimp/jQuery-File-Upload/blob/master/js/jquery.iframe-transport.js https://github.com/blueimp/jQuery-File-Upload/blob/master/js... (it's pretty small).

sc00ter 13y ago

CarrierWave appears to support Rails 4; the rest are not doing anything special other than making jquery js acripts available in the asset pipline without manually installing them, so shouldn't cause any issues. You'll have a bit of work to do to migrate to strong parameters, but you can always add the protected_attributes gem back to re-enable support for attr_accessible. I'd suggest checking out the Rails 4 migration RailsCast.

aaronbrethorst 13y ago
I've been using Carrierwave with Rails 4 RCs and haven't run into any trouble with it.
- jpdoctor 13y ago
  Thank you for this info.