Yes, I am very excited. I should have released during business hours with announcements prepared and whatnot, but I really wanted this code in people's hands. I hope that everyone enjoys this release!
Thanks for yours and everyone else's hard work. This release looks great. Been developing on the RCs the past month or so and appreciate the improvements.
Thanks for linking to the new Asset Pipeline guide. Richard Hulse, Mohammed El-Abid and me put a lot of work into that to try to help people understand how it works.
It's just a fantastic feeling to see something that I've worked on be helpful to so many people. Thank you.
Thanks for the links. From reading the release notes, it looks like there's a lot of changes around the behavior of creating/updating/destroying through active record associations - other than the release notes is there anywhere else that has a good writeup of these changes?
Interestingly DHH is only #2 contrubutor overall, and number 9 this year... (by number of commits; and no, that isn't a perfect measure of contribution)
The 3.1 asset pipeline is great stuff ... but if anyone currently using Jammit is leaning towards switching to the asset pipeline -- for any reason other than it's the default in Rails 3.1 -- I'd be curious to hear about why. I'd like to keep developing Jammit as an alternative approach, as there are differences in philosophy: explicit asset packages vs. in-file dependencies, for example.
Jammit has worked extremely well paired with Barista+Compass, but for a Backbone-heavy app where templates are shipped client-side, it's nice to tack on '.erb' at the end of a template file and use Rails asset helpers for cache-busting and asset host url construction.
Jammit should already be playing well with Rails' built-in cache busting, although I imagine that the situation might change with 3.1's new fingerprinting.
As for having to pipe "static" JS and CSS files through ERB ... I've always thought that was something best avoided by choice, unless absolutely necessary.
Same here. I've been trying out the 3.1 RCs, and I think the asset pipeline has some potential, but I haven't found a replacement for Jammit's JST compilation. (Although I haven't looked very hard. I'm sure there's a solution out there.)
Sprockets includes Jammit-inspired JST support. You can use it with either EJS or Eco templates. See the "JavaScript Templating" section of the readme: https://github.com/sstephenson/sprockets#readme
"Sprockets supports JavaScript templates for client-side rendering of strings or markup. JavaScript templates have the special format extension .jst and are compiled to JavaScript functions"
From sprocket README. Although, I have switched to Rails 3.1 and I am not using asset pipelining at all, just sticking with jammit.
Here is something not in the release notes that people may want to watch out for: The format of the session has changed, the FlashHash class to be precise, so trying to load a browser session created on Rails 3.0 will give a marshal load error on 3.1 if it had anything in the flash.
This means you will want to change your SESSION_KEY variable to expire all sessions, otherwise users that are logged in while you upgrade can get stuck until they clear their cookies. (So I postponed the upgrade to the weekend...)
Thanks! Started learning 3.1 a few months ago and loved the asset pipeline, but had a few problems getting a particular piece to work. Will have to get back to using it soon.
It doesn't track model associations, so can lead to odd behaviour if you don't know the pitfalls. Hopefully having to enable it manually means those who do enable it have read up and know what to expect.
