No, sorry, we haven't written anything about it. It was another guy who
wrote the code as well, so I'm really not the right person to ask :-)
Regards,
Andréas
2017-03-21 8:53 GMT+01:00 Derek :
> Interesting to hear, Andréas. Have you written up any of your experience
>
Interesting to hear, Andréas. Have you written up any of your experience
with the implementation of nested formsets?
On Monday, 20 March 2017 10:57:20 UTC+2, Andréas Kühne wrote:
>
> Yes,
>
> I actually have written an application where we use the django admin
> interface as the primary work
Yes,
I actually have written an application where we use the django admin
interface as the primary work area for the client who uses the system.
We use a lot of specially written actions and widgets, but it is really
versitile. The only problem we have had was when we wanted to do
polymorphism
Good point; with some work (e.g. adding actions), the admin can cover 80 to
90% of what most DB-focused projects will need - the django-suit interface
also makes it look pretty slick!
On Saturday, 18 March 2017 09:54:37 UTC+2, Andréas Kühne wrote:
>
> Yeah I know - the django admin platform is
Yeah I know - the django admin platform is really great - add the grappelli
interface to it and you can use it as a proper backend for a project. :-)
Nice to see that I was able to push you in the right direction.
Regads,
Andréas
2017-03-17 23:22 GMT+01:00 Mike Dewhirst
On 17/03/2017 7:49 PM, Andréas Kühne wrote:
You can override the admin change form for the model you want and then
change the title.
You can check here for some information:
https://docs.djangoproject.com/en/1.10/ref/contrib/admin/#overriding-admin-templates
That's fantastic! Thanks Andréas
You can override the admin change form for the model you want and then
change the title.
You can check here for some information:
https://docs.djangoproject.com/en/1.10/ref/contrib/admin/#overriding-admin-templates
Regards,
Andréas
2017-03-17 5:21 GMT+01:00 Mike Dewhirst
7 matches
Mail list logo