The handling of sprites is really cool. Allowing Rails to generate the sprite from a directory and then calling the sprite image with sprite_tag(folder/sprite) makes sprites much less painful. As a designer, I appreciate the attention to that stuff from the core team.
Thanks, and for the haters, sorry, but I don't do videos. They tend to be a waste of time unless you're there in person; you can't grep them, skim them, focus on parts you're interested in, and all the other convenient things you can do with text.
I haven't watched the video, so perhaps this is answered there. But I'm curious if the preprocessing of CSS is intended to implement some of the functionality available in SASS (like variables in CSS)?
10 comments
[ 3.6 ms ] story [ 34.9 ms ] thread- Brand new router with an emphasis on RESTful declarations
- New Action Mailer API modeled after Action Controller (now without the agonizing pain of sending multipart messages!)
- New Active Record chainable query language built on top of relational algebra
- Explicit dependency management with Bundler
http://guides.rails.info/3_0_release_notes.html
Rails 3.1
- Better organisation for public/*
- Preprocessing CSS and Javascript with .erb templates, helpers for sprites
- Automatic down migrations