Rails 3.2?

[Ed W]

How is AS looking with regards to Rails 3.2?

Thanks

Ed W

[Wes Gamble]

ActiveScaffold?

I don't know :(. Still on 3.0.7.

W

[Sergio Cambra]

Reading changes in rails 3.2 I think it won't be hard to update. However I
haven't tried it, maybe it works.

[Nick Rogers]

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'.

--
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 actives...@googlegroups.com.
To unsubscribe from this group, send email to activescaffol...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/activescaffold?hl=en.

[Sergio Cambra]

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

[Nick Rogers]

Thanks. Could you bump the requirement in your recordselect fork as well?

[Nick Rogers]

There is an exception under rails 3.2 caused by the
active_association_reflection patch that should be resolved.

See this thread

http://groups.google.com/group/activescaffold/browse_thread/thread/fe9d24a9b72adc67