Re: thinking about the admin's scope and its description in the docs

On Tue, Mar 15, 2016 at 1:59 AM, Ramez Ashraf wrote: > > 1. Inlines (FormView is like a teenager playing in the park next to Spartan > Hero) There are inlinemodelformsets you can use outside the admin. > 2. Entry Log change message django-activity-stream or even

Re: thinking about the admin's scope and its description in the docs

Like what is "site front end" that the admin shouldn't replace ?! I work with business application where clients puts data in and get reports back... (Like Sales/Store/Client balances and stuff) I tried to work "my front end" (after getting the bad/wrong message from the docs) but it was so much

Re: thinking about the admin's scope and its description in the docs

+1 -- Aymeric. > On 17 févr. 2016, at 18:16, Marc Tamlyn wrote: > > That looks like a good balanced message to me. > > On 17 February 2016 at 16:57, Tim Graham > wrote: > Here's another try for the docs: > > One of

Re: thinking about the admin's scope and its description in the docs

That looks like a good balanced message to me. On 17 February 2016 at 16:57, Tim Graham wrote: > Here's another try for the docs: > > One of the most powerful parts of Django is the automatic admin interface. > It > reads metadata from your models to provide a quick,

Re: thinking about the admin's scope and its description in the docs

Here's another try for the docs: One of the most powerful parts of Django is the automatic admin interface. It reads metadata from your models to provide a quick, model-centric interface where trusted users can manage content on your site. The admin's recommended use is limited to an

Re: thinking about the admin's scope and its description in the docs

> However, we NEVER had a client that was sufficiently familiar with what a database is or how data modeling works for this to ever suffice. I've got more than two dozen non-technical clients happily using the admin. They also have no familiarity with data modelling but I'm not quite sure how

Re: thinking about the admin's scope and its description in the docs

On 11/02/16 20:11, Andy Baker wrote: > As customisable as it can be, I find the problem to be it is a data-centric view of your system, closely tied to the database models. You're correct that a truly 'task-centric' UI would be a lot of effort - but really - how common are such interfaces in

Re: thinking about the admin's scope and its description in the docs

FWIW, we used to tell clients that Django offers a basic admin interface "for free". However, we NEVER had a client that was sufficiently familiar with what a database is or how data modeling works for this to ever suffice. The first thing we always do on new project is immediately disable the

Re: thinking about the admin's scope and its description in the docs

While I think it's true that a process centric workflow (wizards, or hubs anyone?) would be incredibly useful, that does not take away from the fact that the model centric admins are also incredibly useful, and time saving. It's so easy to add search, sorting, bulk actions, etc to an

Re: thinking about the admin's scope and its description in the docs

> As customisable as it can be, I find the problem to be it is a data-centric view of your system, closely tied to the database models. You're correct that a truly 'task-centric' UI would be a lot of effort - but really - how common are such interfaces in their fullest sense? In reality

Re: thinking about the admin's scope and its description in the docs

On 11/02/16 00:55, Andy Baker wrote: I can't help but feel that the "admin is very rudimentary and hard to customize" is perpetually overplayed by many in the community. Maybe I'm suffering Stockholm Syndrome but I'd like to raise a dissenting voice. I must admit I'm a large proponent of

Re: thinking about the admin's scope and its description in the docs

On Wed, 10 Feb 2016 at 13:55 Andy Baker wrote: > I can't help but feel that the "admin is very rudimentary and hard to > customize" is perpetually overplayed by many in the community. Maybe I'm > suffering Stockholm Syndrome but I'd like to raise a dissenting voice. > > I find

Re: thinking about the admin's scope and its description in the docs

Just to follow up - I think the biggest improvements I've yearned for are fairly simple and unlikely to break backwards compatibility: 1. Break up the remaining monolithic methods to allow easier overriding (this is much better nowadays but a few beasts remain) 2. More blocks in the templates

Re: thinking about the admin's scope and its description in the docs

I can't help but feel that the "admin is very rudimentary and hard to customize" is perpetually overplayed by many in the community. Maybe I'm suffering Stockholm Syndrome but I'd like to raise a dissenting voice. I find it the quickest and most efficient way to provide an admin interface for

Re: thinking about the admin's scope and its description in the docs

On Tue, 9 Feb 2016 at 23:25 Tim Graham wrote: > The introduction to the admin in the docs [0] reads: > > "One of the most powerful parts of Django is the automatic admin >> interface. It reads metadata in your model to provide a powerful and >> production-ready interface

Re: thinking about the admin's scope and its description in the docs

Hello, Il 10/02/2016 00:25, Tim Graham ha scritto: The introduction to the admin in the docs [0] reads: "One of the most powerful parts of Django is the automatic admin interface. It reads metadata in your model to provide a powerful and production-ready interface that content

Re: thinking about the admin's scope and its description in the docs

On Wed, Feb 10, 2016 at 7:25 AM, Tim Graham wrote: > The introduction to the admin in the docs [0] reads: > > "One of the most powerful parts of Django is the automatic admin >> interface. It reads metadata in your model to provide a powerful and >> production-ready

thinking about the admin's scope and its description in the docs

The introduction to the admin in the docs [0] reads: "One of the most powerful parts of Django is the automatic admin interface. > It reads metadata in your model to provide a powerful and production-ready > interface that content producers can immediately use to start adding > content to the