News for hackers. Stuff that matters.
Re:Rails 4.0: Final version released by psychometry on Tuesday June 25, 2013 @10:54AM (#5939861)
Depends on the size of your Gemfile. There will inevitably be gems that have unpatched Rails 4 bugs.
Re:Rails 4.0: Final version released by jpdoctor on Tuesday June 25, 2013 @11:00AM (#5939908)
> 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.
Re:Rails 4.0: Final version released by sc00ter on Tuesday June 25, 2013 @11:49AM (#5940303)
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.

Re:Rails 4.0: Final version released by aaronbrethorst on Tuesday June 25, 2013 @11:57AM (#5940361)
I've been using Carrierwave with Rails 4 RCs and haven't run into any trouble with it.
Re:Rails 4.0: Final version released by jpdoctor on Tuesday June 25, 2013 @01:06PM (#5940869)
Thank you for this info.
Re:Rails 4.0: Final version released by davidw on Tuesday June 25, 2013 @11:08AM (#5939968)
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.
Re:Rails 4.0: Final version released by fbuilesv on Tuesday June 25, 2013 @02:00PM (#5941270)
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/Frequentl... or directly in the source: https://github.com/blueimp/jQuery-File-Upload/blob/master/js... (it's pretty small).

Re:Rails 4.0: Final version released by jpdoctor on Tuesday June 25, 2013 @11:28AM (#5940134)
> 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.

Re:Rails 4.0: Final version released by ebiester on Tuesday June 25, 2013 @11:31AM (#5940158)
Unfortunately, that's the necessary hack, as far as I know, if you want to have an ajax submission.