Looks like I'm going to have to break up with Typus.
We had a long run, Typus, no regrets…
Active Admin - The missing administration framework for Ruby on Rails
11–20 of 45 posts
Re: Active Admin - The missing administration framework for Ruby on Rails
#12Awesome!
For future reference, you're being downvoted because Hacker News has traditionally looked down upon non-contributive, vacuous one-word comments. Particularly if they looked like they're coming from new accounts to try to boost the article's ranking.
Since you appear to be one of the developers on this project, I think it would have been better received if you had introduced yourself as such.
Re: Active Admin - The missing administration framework for Ruby on Rails
#13I've been having good luck with rails_admin[1], which is currently in the process of receiving a nice facelift[2]. [1] https://github.com/sferik/rails_admin/ [2] https://github.com/sferik/rails_admin/issues/317
I've been digging into RailsAdmin for a project recently as well, and really liking it so far.
A couple things I'd like to see addressed from the author:
- How is Active Admin's approach different?
- Why would someone choose Active Admin over RailsAdmin?
Re: Active Admin - The missing administration framework for Ruby on Rails
#14Awesome!
For future reference, you're being downvoted because Hacker News has traditionally looked down upon non-contributive, vacuous one-word comments. Particularly if they looked like they're coming from new accounts to try to boost the article's ranking. Since you appear to be one of the developers on this project, I think it would have been better received if you had introduced yourself as such.
Oh... Ok, I will introduce myself before saying that Active Admin is awesome from now on.
Re: Active Admin - The missing administration framework for Ruby on Rails
#15[deleted]
Re: Active Admin - The missing administration framework for Ruby on Rails
#16I've been having good luck with rails_admin[1], which is currently in the process of receiving a nice facelift[2]. [1] https://github.com/sferik/rails_admin/ [2] https://github.com/sferik/rails_admin/issues/317
I've been digging into RailsAdmin for a project recently as well, and really liking it so far. A couple things I'd like to see addressed from the author: - How is Active Admin's approach different? - Why would someone choose Active Admin over RailsAdmin?
I would love to know what the differences are too. Although, to be honest, I have stopped using RailsAdmin mainly because of deprecation issues.
Also, it wasn't as nice as I would have wanted.
But this one looks really nice.
Re: Active Admin - The missing administration framework for Ruby on Rails
#17Earlier quoted context omitted.
For future reference, you're being downvoted because Hacker News has traditionally looked down upon non-contributive, vacuous one-word comments. Particularly if they looked like they're coming from new accounts to try to boost the article's ranking. Since you appear to be one of the developers on this project, I think it would have been better received if you had introduced yourself as such.
Oh... Ok, I will introduce myself before saying that Active Admin is awesome from now on.
As I've painfully discovered myself, being humorous, especially sarcastic or filled with dry humor often attracts downvotes too, no matter how funny you thought the joke was.
Re: Active Admin - The missing administration framework for Ruby on Rails
#18I've been having good luck with rails_admin[1], which is currently in the process of receiving a nice facelift[2]. [1] https://github.com/sferik/rails_admin/ [2] https://github.com/sferik/rails_admin/issues/317
I've been digging into RailsAdmin for a project recently as well, and really liking it so far. A couple things I'd like to see addressed from the author: - How is Active Admin's approach different? - Why would someone choose Active Admin over RailsAdmin?
That's a great question and something I plan on writing a full blog post about. But, from a high level, here are the projet goals we've been working with:
1. An administration interface must be good looking and easy to use. The interface is not for developers who understand the underlying data model, rather for operations staff who need to do their job and service our customers.
2. Administration of a production application is way more complex than a simple CRUD of database tables. Although editing data is necessary, most of the time operations staff are finding a resource and performing an action on it or looking up historical data.
3. An administration framework must be highly customizable. Active Admin makes it easy to add controller actions, sidebar elements, action buttons, dashboard widgets, custom forms, show screens and hook in to all resources via plugins.
Re: Active Admin - The missing administration framework for Ruby on Rails
#19I've been having good luck with rails_admin[1], which is currently in the process of receiving a nice facelift[2]. [1] https://github.com/sferik/rails_admin/ [2] https://github.com/sferik/rails_admin/issues/317
I've been digging into RailsAdmin for a project recently as well, and really liking it so far. A couple things I'd like to see addressed from the author: - How is Active Admin's approach different? - Why would someone choose Active Admin over RailsAdmin?
Right now it looks* like rails_admin is a bit more feature complete as far as CRUD administration goes (+ history of edits). While ActiveRails has feature like comments which may be more relevant to less technical users.
* Disclaimer: I'm more familiar (and probably biased) with rails_admin
Re: Active Admin - The missing administration framework for Ruby on Rails
#20There seems to be some layout issues in Firefox 4 (Mac OS).