what's your plan?

[Richard Zheng]

Hi,

If you follow the recent postings, you probably ponder the future plan. What would you use if you have a new rails 3 project coming up? vhochstein suggested rails_admin. I have done some research. It is hard to get an objective view since most people are only familiar with one project. I guess the number of followers on github might a good indicator. Here is some of them,

• active_scaffold: 712
  
• rails_admin: 1514
• typus: 707
• admin_data: 393

What do you think?

Thanks,
Richard

[Michael Latta]

The big differentiator between ActiveScaffold and things like rails_admin is that AS builds controllers that can be used in production UI contexts.  While the other tools all built the controller and all the navigation, which means if you want to fit into a larger production quality site with integrated navigation you are out of luck.  I tried several briefly before returning to AS.  None of them produced UI I was willing to present to a client, while AS does.  Also do not underestimate the value of AS being in the field for 3 years.  Production tested code has value even if it is not as current or elegant as some of the new kids on the block.

Michael

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

[Wes Gamble]

I concur with Michael.  All of my admin. is built with ActiveScaffold and it is nearly trivial to implement.

Wes

[Hernan Astudillo]

Same here. After vhochstein mention rails_admin, i decided to take a look. At first glance, rails_admin is better at getting data admin with layout, menu and autentication running very fast. However, it doesn't have the power of full customisation that AS got. So, if you want a very simple thing and very quick, and don't care for clients asking for special features, you could be ok with rails_admin. But if you think it might grow, go for AS. As for production mode, dunno really about rails admin,  but for AS, i've put that with thousands of concurrent users and working flawlessly. You only have to worry about good server and amount of RAM.

Don't know why rails_admin is more popular since isn't as powerful as AS. Might be that veeery old www.activescaffold.com?

Nano

[Ed W]

On 18/03/2011 03:43, Hernan Astudillo wrote:
> Don't know why rails_admin is more popular since isn't as powerful as
> AS. Might be that veeery old www.activescaffold.com

> <http://www.activescaffold.com>?

I put in my 2p on the reasons in another post, but I think it's mainly

a) that old .com website which makes the project feel a bit dead

b) lack of regular advocacy (blog posts, release announcements) that hit
the rails community (after all this is why you know about rails_admin...)

c) mailing list which requires manual verification of new users (it was
added to stop large amounts of spam which were coming through - perhaps
there is a compromise solution though?)

I think all of these are fixable though. As you say AS is a very stable
chunk of code and largely I think we are in maintenance mode. I would
like to see some improvements in some key internals to make it thread
capable (no globals) and also to streamline the way we generate the
templates to reduce memory usage (causes GC thrashing on my performance
profiling), but largely I see new features being implemented through
plugins and the core code becoming more plugin friendly as a result...

I really hope we can hook Volker in to continue to maintain his rails3
branch, but under the AS repo rather than his own. I also don't want to
chase him away since he's obviously only got limited time and faith in
the continuation of this project?

Fingers crossed. Here's hoping

Cheers

Ed W