Rails 3 branch
davout
do you have any plans to create a Rails 3 branch ?
i'd love to help towards getting *official* rails 3 support
Sergio Cambra .:: entreCables S.L. ::.
Yes, I will create a rails3 branch, but I can't say when I will do it. I have
started to migrate a simpler plugin and an application to learn something
about rails3. It would be useful to have more tests to avoid breaking
features, I added some of them some weeks ago.
--
Sergio Cambra .:: entreCables S.L. ::.
Mariana Pineda 23, 50.018 Zaragoza
T) 902 021 404 F) 976 52 98 07 E) ser...@entrecables.com
davout
Well, the sooner you create the branch, the sooner i'll be able to
submit patches
Most of my apps depend heavily on AS, I started to migrate them to
Rails 3 using Volker's fork with mixed success.
So I'm pretty motivated to put effort into getting AS officially
supporting R3.
Also, (but maybe it's a debate that's already been gone through) I'd
love to make AS usable as a gem too.
Let me know when I'll get to start =)
On 27 sep, 14:15, "Sergio Cambra .:: entreCables S.L. ::."
nicolae.claudius
vhochstein's fork is rails3 compatible and supports bot prototype and
jquery
http://github.com/vhochstein/active_scaffold
http://github.com/vhochstein/active_scaffold/wiki
http://vhochstein.wordpress.com/2010/08/28/setupactivescaffoldrails3/
If anyone is kind to consider the following features in rails3 branch
I would be grateful:
* decouple AS from ActiveRecord, to be usable with other ORM's too (ie
Mongoid), maybe by having a pluggable model.column API
* thread-safe: no controller writable class variables, maybe by using
things like cattr_accessor to have controller level configuration that
gets copied to instances on their creation. This would allow thread-
safe-per-request configuration tweks instead of
http://github.com/activescaffold/active_scaffold/wiki/per-request-configuration
(change globals the change them back ...)
davout
wrote:
>
> vhochstein's fork is rails3 compatible and supports bot prototype and
> jquery
> If anyone is kind to consider the following features in rails3 branch
> I would be grateful:
> * decouple AS from ActiveRecord, to be usable with other ORM's too (ie
> Mongoid), maybe by having a pluggable model.column API
> * thread-safe: no controller writable class variables, maybe by using
> things like cattr_accessor to have controller level configuration that
> gets copied to instances on their creation. This would allow thread-
Sergio Cambra .:: entreCables S.L. ::.
> On 29 sep, 16:34, "nicolae.claudius" <claudius.nico...@gmail.com>
>
> wrote:
> > Note worthy:
> >
> > vhochstein's fork is rails3 compatible and supports bot prototype and
> > jquery
>
> Yep, that was implied by "using volker's fork" =)
>
> > If anyone is kind to consider the following features in rails3 branch
> > I would be grateful:
> > * decouple AS from ActiveRecord, to be usable with other ORM's too (ie
> > Mongoid), maybe by having a pluggable model.column API
>
> Relying on ActiveModel API would do the trick i guess, wouldn't it ?
I don't think it's possible. ActiveScaffold does much with associations, and
associations aren't ActiveModel API. It needs reflect_on_all_associations and
check association macro, so that code would be different for each ORM. I will
try to decouple code related to associations, so a module for Mongoid can be
developed.
>
> > * thread-safe: no controller writable class variables, maybe by using
> > things like cattr_accessor to have controller level configuration that
> > gets copied to instances on their creation. This would allow thread-
> > safe-per-request configuration tweks instead
> > ofhttp://github.com/activescaffold/active_scaffold/wiki/per-request-con..
> >. (change globals the change them back ...)
>
> Wouldn't that be a significant performance eater ?
I have thought about that, I would like to have proxy configuration models as
instance variables, which will read class configuration unless you override
(set) some configuration option. However, I haven't started it and I don't know
how hard it will be.
Atastor
works great, but obviously there are deviations from your master
branch, the deviations mainly consisting of not-yet-pulled commits of
your branch.
Regards
Michael
On 27 Sep., 14:15, "Sergio Cambra .:: entreCables S.L. ::."
Sergio Cambra .:: entreCables S.L. ::.
> How far will you base your r3 branch on volkers branch? His branch
> works great, but obviously there are deviations from your master
> branch, the deviations mainly consisting of not-yet-pulled commits of
> your branch.
>
> Regards
> Michael
>
I'm not sure, I would have to look at his branch.
Ed W
> On Lunes, 27 de Septiembre de 2010 12:16:28 davout escribió:
>> Hi Sergio!
>>
>> do you have any plans to create a Rails 3 branch ?
>> i'd love to help towards getting *official* rails 3 support
> Yes, I will create a rails3 branch, but I can't say when I will do it. I have
> started to migrate a simpler plugin and an application to learn something
> about rails3. It would be useful to have more tests to avoid breaking
> features, I added some of them some weeks ago.
>
I thought this was interesting (and somewhat relevant)
I do agree though that it would be useful to get a rails-3 branch in the
official repo as soon as possible - even if it has no new code in it
then at least other forks can fork from that rather than trying to
rebase against a 2.3 branch? Hopefully that way contributions will come
back faster as well?
I would be happy to fund some development time on this?
Cheers
Ed W
Ed W
> I thought this was interesting (and somewhat relevant)
Dur, it appears I forgot the link...