I made sure web-app-theme works with rails 3.0 and rails 3.1. Furthermore I fixed the specs so the generators are tested more. I did not check the cucumber features.
Use bundler to manage dependencies.
Fixed the rspec tests (using a dummy rails project --enginex).
Enabled the rake tasks again.
Ignore unneeded files.
Use generator_spec for easy testing of generators.
Simplified a bit.
Test the default case: no params.
Apply explicit global scoping
Clean up the require statements.
Copy to rails 3.1 specific paths (+test).
Make sure the default application layout uses the rails 3.1 assets pi…
…peline as well.
Excellent! when would this be merged?
Changed to use spec files
Merge pull request #1 from coupacooke/patch-1
Fixed test directory references
Merge remote-tracking branch 'upstream/master'
@nathanvda, can you please rebase it to 0.7.0. Your fork does not contain Activo 2 theme and it will also be easier for @pilu to pull. I've done this for ourselves in our fork, but I'm sure others would love to point your Gemfile's to your fork until it gets pulled into an official version.
Merge branch 'master' of github.com:nathanvda/web-app-theme
Make sure that the images/fonts are copied so that they can be picked…
… up correctly in rails3.1 (without having to edit the stylesheets).
I had some troubles getting the default (activo-2) working correctly. I got it to work (without needing to edit any stylesheet) if i copied the images and fonts (under stylesheets) to app/assets/images. Not sure if this is the wanted approach, but this way at least is the easiest to maintain backward compatibility.
The 'problem' is that the default JS and CSS assets are combined into application.js and application.css in Rails 3.1, so any relative paths will be relative to that, even if they were originally pulled in by Sprockets from a subdirectory by require_tree .. I think in many cases (such as internal applications), pulling in web-app-theme separate from the combined assets is fine, but it needs changes to the default application.css.