DjangoAdmin 2.0 - rewrite of django.contrib.admin

https://github.com/twoscoops/django-admin2

by pajju • 13 years ago

96 29 13 years ago

github.com

wiremine• 13 years ago

In general, my take is: 'bout time.

Even if this particular project doesn't make it into django.contrib, it is nice to see movement in this area.

IgorPartola2• 13 years ago

It never will:

  Requirements
    Django 1.5+
    Python 2.7+ or Python 3.3+
    django-braces
    django-extra-views
    django-floppyforms
    django-rest-framework
    Sphinx (for documentation)

Django comes all bundled together or not at all. IIRC, this was one of the reasons why bcrypt wasn't enabled for so long: the canonical Python library came bundled with C code.

I am excited for this, but I don't see it going into django.contrib.

andrewingram• 13 years ago

FYI: I wouldn't be surprised if the parts of django-braces and django-extra-views we're using end up making it into django.core. As for the other dependencies (floppyforms and rest-framework), I'm sure there'll be further discussions if and when we start pushing for inclusion in django.contrib.

huxley• 13 years ago

I think the versions of Django or Python don't play into it, if it was to be included in contrib it would probably happen around Django 1.7+. By then Python 2.7/3.3 will likely be the minimum required versions of Python.

Django's docs already use Sphinx as an optional install.

Django-braces and Django-extra-views are excellent but modest extensions to Django's class-based views and would likely either become part of Django or be good starting points for extending Django's generic CBV IMHO.

So the only really controversial additions would be django-floppyforms and django-rest-framework.

I seem to recall that there has been talk in recent years about all or parts of contrib being de facto split-off from core (as opposed to the technically distinct but included status of being a contrib module), so that might factor into it too.

hacliff• 13 years ago

Great project, the standard django admin regularly feels too 'magical', try to do anything custom and you're screwed.

mazelife4• 13 years ago

I don't know about that. I've customized the heck out of that thing (e.g. https://github.com/mazelife/django-scaffold) and it's quite possible, although you'll need to be pretty familiar with the source code. That said, this particular part of Django is definitely starting to show its age. Compare the look-and-feel and UI with something like ActiveAdmin (http://activeadmin.info/) for Rails and you'll see what I mean. What's more, the approach to "class-based views" feels disconnected to the way Django apps are written now.

zalew2• 13 years ago

Compare the look-and-feel

http://grappelliproject.com/

amirouche2• 13 years ago

I don't know about that.

1) (minor) Getting into templates to add an action e.g. «export as CSV» is a lot to ask. (Anything that leads me into changing the templates is, at least for me, a no, except form ergonomy which is in Django regularly done in an API/DSL based on nested dict, list and attributes.)

2) (minor) Custom models (non django.models.Model) or specifiq models (like django scaffold) in the ObjectList aka. ChangeList or in the Form view is not possible which means no mongodb, no kv store, no to anything that hasn't a proper Django's model backend even if in the end it's all about class properties and most of the time slice queries.

3) (major) The admin ergonomy and plugability is poor, you can not choose the way pages feet together, for instance and the primary concern is that the first page must be a list of models regrouped by apps. This is in advanced apps a non sens, most likely when you use a lot of reusable apps, where the code doesn't reflect the end-user experience, the admin will look ugly. But should the admin reflect or map somehow the end-user experience ? It's a complex mapping, the workflow of the admin is elaborate and depends of the app... otherwise said the Django «generated» admin is the equivalent of a spreadsheet compared to specific domain admin areas.

I've customized the heck out of that thing (e.g. https://github.com/mazelife/django-scaffold)

Does it support filters and actions ? because what it looks like you did is that you are feeting a view to the admin API, leaving the elaborate actions and points of customisation on the side.

and it's quite possible,

It our job to make things possible.

although you'll need to be pretty familiar with the source code.

You mean read the code ? It's not that difficult. Also I think django admin reworks bring more clarity.

That said, this particular part of Django is definitely starting to show its age.

In terms of features or skin ?

Compare the look-and-feel and UI with something like ActiveAdmin (http://activeadmin.info/) for Rails and you'll see what I mean.

Definetly looks like a customised Django Admin. Also Django Admin already had it's skin war, the feature/API war is barely starting.

What's more, the approach to "class-based views" feels disconnected to the way Django apps are written now.

What do you mean ?

joelhaasnoot• 13 years ago

Custom is fine, but if it's not model-oriented CRUD+x (where x is any other atomic action on a model object) it doesn't work well.

andybak• 13 years ago

I'd like to hear some specifics. Over the last six years I've surveyed and sampled a wide range of extensions, add-ons and integrations into the admin and it's proved astonishingly flexible so far.

Yes - there's things that people would probably do differently now and it's overdue for an overhaul but the degree of extensibility they managed to enable with the initial design decisions was fairly incredible.

googletron• 13 years ago

are there screenshots for the new admin?

phatbyte• 13 years ago

This. If you are showing off a more visual oriented project, screenshots are a must.

sonar_un• 13 years ago

Ok, I just installed it and took a screenshot!

Here you guys go!

http://imgur.com/AmKrYDN

amirouche2• 13 years ago

this https://github.com/sshwsfc/django-xadmin also looks good. direct link to demo http://x-demo.herokuapp.com/

vanwilder77• 13 years ago

Great job!! Looks cool

Siecje• 13 years ago

My issues with the default admin are:

1)You can't add text to a page. I want to add information from another model. For example a field of a foreign key model.

What I currently do is put that in the __unicode__ function, but it has no context as to what it is. Then in the rest of my site(outside of admin) I use the values directly. print (model.name) instead of print (model)

2) You can't put display return values of model methods. You have to create property values. But property values are not query sets so you can't really use them, but don't realize that you need .filter until your site is super slow.

3) Inline form validation is magical. You can't just add validation to an inline form, you have to do this http://pastebin.com/CGjLX2vf

4) You can't search in foreign key form fields. I have a M2M foreign key field and when I select I have to hold ctrl and scroll with this tiny scroll bar the size of my mouse cursor and I have hundreds of items in the field.

Please let me know if I am just doing it wrong.

whubr2• 13 years ago

1. You can use custom admin templates (just override the necessary blocks)

2. Not sure what you mean :)

3. Yes, this is a little awkward

4. You need filter_horizontal or filter_vertical: https://docs.djangoproject.com/en/dev/ref/contrib/admin/#dja...

kmike84• 13 years ago

You can do (1) and (2) using readonly_fields (see https://docs.djangoproject.com/en/dev/ref/contrib/admin/#dja... ). For (4) use raw_id_fields (https://github.com/lincolnloop/django-salmonella app could be also helpful).

whubr2• 13 years ago

Salmonella is awesome but doesn't play well with multiple admin sites.

darwinia• 13 years ago

Good to know! BTW, this one worth also trying. http://djangosuit.com/ (it's not my project)

DjangoAdmin 2.0 - rewrite of django.contrib.admin

Related Stories