allanjamesvestal / django-linnaeus Goto Github PK

The process for doing this is gonna kind of suck, I imagine.

I'm specifically thinking of a 'map' button for the data streams.

You could do this by creating an admin.ModelActionButton object in the relevant admin.py. It would require the action name, icon and sub-URL (off the base one for this model, exempli gratia /datastream/data/fire_dispatches/dispatch/map/).

The object would also be able to accept the ID of a permission object to decide whether users could take that action. This would determine if users could see that extra button. Finally you could set a priority for the button, to determine whether it would show up to the left or the right of the others.

Then you'd tie that into the existing add and change buttons by configuring an index_model_actions setting on the model (it would default to new representations of the existing buttons); you could also then import one or both of those and show just what you wanted to).

Finally you'd want to set the main link on an app to perform one of the buttons' action. You'd have another configurable setting like index_model_default, which would itself default to the standard change action.

Just as it says. You could have three models from three apps and it would look like they were all from one. This would be relatively easy to do with an option like show_models_by_app, which could default to being true. You'd still have apps enumerated in the URL, but otherwise this would be quite simplifying.

Eventually you could also hide app names from the breadcrumbs if this or a similar switch is flipped. (I'd say have a show_app_in_breadcrumbs that would default to the same bool value as the above, except of course on app index pages.

Each model's admin could have a setting front_page_view which would replace the standard "model add change" slot with expanded or tailored information.

You'd need at least three settings: front_page_view for the topmost admin page, type_page_view for the per-type list and app_index_page_view for the per-app-and-type list. (There'll be sane defaults, so if you want all three you can just set front_page_view and if you want the last two you can set type_page_view.)

Add description and installation instructions to the former and lists of available linnaeus_conf options to the latter.

Have a hidden_from_index param in each TypeConfig (with a default of false) that, if selected, would keep all models in a given category from showing on the index page (they'd still be accessible direct from their URLs assuming a user had requisite permissions to change them).

To include removal of admin.site.root_path from available options [replaced with reverse('admin:front-page')], tweaks to filter_horizontal and _vertical M2Ms, date/time widgets and maybe more.

This mainly means having a sidebar template separate from Nando's announcements (and maybe having the option to take the index pages full-width instead of having a sidebar).