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 On Mar 11, 2011, at 12:53 PM, Richard Zheng wrote: > 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 > > > -- > 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. -- 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.
