Proposal: make app index optional

56 views
Skip to first unread message

Michel Thadeu Sabchuk

unread,
Dec 27, 2011, 9:57:11 AM12/27/11
to Django developers
Hi guys,

Me and some grappelli developers are talking about the possibility of
grappelli make the app index optional. This would be very useful once
I can customize the index page and therefore, sometimes the app index
messy the things reather than organize access.

We all agree that this configuration would make much more sense to
exist in django reather than in the grappelli. I can customize the
index page without grappelli anyway.

What do you think about it?

Best regards,

--
Michel Sabchuk
http://turbosys.com.br/

patrickk

unread,
Dec 27, 2011, 12:57:47 PM12/27/11
to django-d...@googlegroups.com
IMO this issue is not related to grappelli whatsoever.

the question is, if the app-index makes sense to an editor? and I think that this not the case – because an editor doesn´t need know what an "app" (within a django-project) is.
my experience is that editors are extremely confused about the whole "app-thing" ... esp. with the index-page which is a list of "INSTALLED APPS" which is hard to explain to someone responsible for the content of a website.

if the admin-interface is for developers, the app-index does make sense.
if the admin-interface is for editors, the app-index doesn´t make sense at all.

best,
patrick

Russell Keith-Magee

unread,
Dec 29, 2011, 2:06:20 AM12/29/11
to django-d...@googlegroups.com
On Tue, Dec 27, 2011 at 10:57 PM, Michel Thadeu Sabchuk
<mich...@gmail.com> wrote:
> Hi guys,
>
> Me and some grappelli developers are talking about the possibility of
> grappelli make the app index optional. This would be very useful once
> I can customize the index page and therefore, sometimes the app index
> messy the things reather than organize access.
>
> We all agree that this configuration would make much more sense to
> exist in django reather than in the grappelli. I can customize the
> index page without grappelli anyway.
>
> What do you think about it?

I'm sure the devil will be in the details, but as a broad goal, this
seems reasonable to me.

There's a lot of room for Django to "eat it's own dogfood" when it
comes to the admin interface; making individual views class based,
making it easier to reuse parts of views, and so on. If this sort of
refactoring were to happen, it would seem logical that improved
configurability of these views (e.g., making the "home" view
user-configurable) would be a logical outcome.

There were some discussions at DjangoCon US 2011 about starting a
"Django NewAdmin" as a broad development effort; however, this doesn't
appear to have generated any massive development effort. If this is an
area that you would like to help out, feel free to pitch in!

Yours,
Russ Magee %-)

Michel Thadeu Sabchuk

unread,
Jan 3, 2012, 10:16:58 AM1/3/12
to Django developers
Hi Russ,

> it would seem logical that improved
> configurability of these views (e.g., making the "home" view
> user-configurable) would be a logical outcome.

In fact, I propose an configurable option to keep backward
compatibility but, in a refactoring, I would suggest to get rid of the
app index completely ;)

> There were some discussions at DjangoCon US 2011 about starting a
> "Django NewAdmin" as a broad development effort; however, this doesn't
> appear to have generated any massive development effort. If this is an
> area that you would like to help out, feel free to pitch in!

Of course! How can I help?

Best regards,

Michel Sabchuk
http://turbosys.com.br/

Reply all
Reply to author
Forward
0 new messages