On Viernes, 27 de enero de 2012 11:13:37 Nick Rogers escribió: > I spent the last month upgrading my rails 3.0 app to 3.1, including the > asset pipeline. I use active_scaffold heavily (~170 active scaffold > controllers). > > I am now in the process of upgrading to 3.2. The good new is, everything > active_scaffold wise seems to work without changes. The only changes > necessary were modifying the gemspecs to require rails >= 3.1 instead of > ~3.1.0 > > I'm using the following trees: > git://github.com/vhochstein/render_component.git > git://github.com/scambra/recordselect.git > git://github.com/activescaffold/active_scaffold.git > git://github.com/naaano/active_scaffold_export.git > git://github.com/courtland/active_scaffold_batch.git > > I had to change the gemspec for the following: > active_scaffold (official master) > > render_component (volkers fork, although inline scaffolds seem to work on > 3.2 using official active scaffold and AJAX method of inline rendering, > that is without render_component). > > recordselect (sergios fork). > > Everything seems to work, including: inline scaffolds, recordselect, > active_scaffold export, active_scaffold_batch, jquery timepicker, > > Sergio and Volker, do you think we could change the gemspecs to require '>= > 3.1.3' instead of '~ 3.1.0'.
This is great news I will change it now and release 3.1.18 -- You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/activescaffold?hl=en.
