Feature: Models marked as readonly shouldn't allow save buttons in Edit view

[jc00ke]

First, thanks, because rails_admin is awesome.

Business:
It would be nice if the rails_admin Edit view did not display the save buttons when model.readonly? # => true

Right now if the model is readonly then an ActiveRecord::ReadOnlyRecord error is thrown when attempting to save.

I might also expect that all form fields on such a model are automatically marked as read_only.

Thoughts? Thanks!

[combizs]

Rails admin is such an awesome tool.

With regards to this issue, I would like to work on this. I installed it with a simple blog app and it works great. One thing I noticed is that if we disable the buttons, it would prevent the form from submitting. I would like to further enhance the user experience by fading-out the buttons on this page, along with other buttons/tabs on related pages as well. Attached contains multiple screenshots, pasted into one image, of the admin "dashboard" page, the "list of posts" page, and "details of post" page. The circles I drew on top of that layer describes the notion to disable the feature to avoid admin confusion.

Please let me know your thoughts. I am already starting to work towards a practical solution.

[pducks32]

So I would like to work on this because this feature would be really helpful for something I'm working on. As for the UX, I'm wondering what might be better. Not showing the buttons at all or having them disabled?

[inopinatus]

This was an incomplete idea, because readonly? isn't forever and can be dynamic, including based on field values, which means you can edit it to not be read-only any more. In Rails it's only evaluated at the moment of save, but rails_admin has now made it matter at the moment of view.

Now I have to figure out how to tell rails_admin that it's okay to allow editing of a particular readonly? object.