When trying to fix ticket #14087, I got an idea on how to separate out
all contrib apps.
Make django.contrib a namespace package. Every django release just
ship one more package which does not bundle any contrib apps. The
other one just bundle latest stable versions of contrib apps. Thus
contrib a
On Sat, Feb 4, 2012 at 11:23 AM, Ric wrote:
> no no, my point is not to remove admin, you misunderstood me...
>
> what i'm talking about is the extend the current admin version, with a
> theme framework.
>
> the theme framework got a default theme, that is the current admin
> theme, but then deve
@Łukasz : Thanks a lot for the response. But as Henrique mentioned using
the __init__()in the view class and then returning a JSON response would be
server side right ? Or Am i missing something here ?
I was thinking something on the lines of this. Add an
attribute in django.forms.
no no, my point is not to remove admin, you misunderstood me...
what i'm talking about is the extend the current admin version, with a
theme framework.
the theme framework got a default theme, that is the current admin
theme, but then developers can add their own theme.
now making a theme for dj
On Feb 4, 11:26 am, "Adam \"Cezar\" Jenkins"
wrote:
> In this thread. There is a lot of mistaking of an app being installed with
> Django vs. an app being in the same code repo as Django.
Wouldn't this mean there are all the same dependencies for default
install? What about backwards compatibilit
In this thread. There is a lot of mistaking of an app being installed with
Django vs. an app being in the same code repo as Django.
Don't worry people. I don't think anyone is seriously considering throwing
away the admin.
On Fri, Feb 3, 2012 at 6:55 PM, Joe & Anne Tennies wrote:
> I'll throw in
