Adapt to new structure introduced in jQuery UI 1.11.0

[rosenfeld]

I gave it a try. It builds the assets and they seem to be correctly generated. But I didn't actually test the generated gem yet, while I intend to do it tomorrow. Anyway, there are lots of incompatible changes proposed in this PR to consider.

[rosenfeld]

I've just tested the changes in this PR and they worked for my application after changing the way I required jquery-ui in my assets.

[joliss]

Thanks!

Hm, the comment at the very bottom of the README re collision with jquery-rails still applies, doesn't it? jquery-ui.js was only removed from jquery-rails last year, and it seems the old jquery-rails version might still be used quite widely.

[joliss]

Do you think we can/should start using the jquery-ui.js name already?

[skateinmars]

I think it's been long enough since the renaming in jquery-rails that we can go ahead and use the "proper" file names.
The major version of the gem should be bumped though and the README updated accordingly.

I haven't checked the PR but from what I understand the latest jquery-ui release has a different file hierarchy? In this case this is a good opportunity to change the gem and follow the new naming conventions.

[rosenfeld]

I can't think of an user that would like to keep up-to-date with jQuery UI but not with jQuery... They would be able to use up to jQuery UI 1.10.x anyway. I think the jQuery UI structure scheme change is a good opportunity for breaking backwards compatibility, don't you think?

[joliss]

Hm, yes. Maybe we can just add a warning not to use jquery-rails <3.0.0.

[rosenfeld]

That makes sense to me

[joliss]

There is a stray puts here... Could you review the diff line-by-line please and make sure it's exactly the code you intended?

I believe the test app (in the testapp directory) needs updating as well for the new file names.

Let me know when you've re-pushed and I'll take a look again so we can merge this. Thanks again for putting this PR together! :)

[rosenfeld]

Sorry, will fix that. I haven't noticed the testapp directory before. I'll try to figure out how this is intended to be used...

[rosenfeld]

I moved the constant to a method to avoid reprocessing it for every rake task or command like rake -T.

[rosenfeld]

I've fixed the testapp to work with the recent changes and pushed all changes. I've added db/schema.rb to the testapp's .gitignore as the file didn't exist in the repository and it's created upon rake db:migrate.

[joliss]

Awesome, thanks Rodrigo! I've merged this and released it in version 5.0.0.

[rosenfeld]

Thank you very much, Jo :-)