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 django is an hack, and not an hook, because some javascript are hard coded inside django admin. i'm thinking about jquery, django use 1.4, i need 1.7 for my javascript, and i've done a terrbile hack to remove js from admin. what i'm talking about is creating a single place in django to register stylesheet and javascripts, and then inject them in every context with an optional context processor. using a request.media attr, would allow admin to add on the fly style and js for horizontal filters and fancy widget. then for developers would be more simple to create and mantain a separete bootstrap theme. On 4 Feb, 11:16, Anssi Kääriäinen <[email protected]> wrote: > On Feb 4, 11:26 am, "Adam \"Cezar\" Jenkins" <[email protected]> > 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 compatibility, can Django include > something by default which has its own versioning policy? How does > this even work with regards to tarball downloads, which is probably > still the most common way to install Django in the new users category. > That happens to be the category who are most hit by removal of Django > from contrib. > > If this would be done, it would mean a radical sift in the way Django > is distributed. Tutorial step 3 should be changed from talking about > the admin to talking about how to use PIP, virtualenv and where to > find nice packages. Using django-admin2 as an example. Maybe this > could work and would actually benefit Django development. But this is > a radical change from "download this tarball and off you go, batteries > included, backwards compatibility for 2 releases guaranteed" > philosophy. > > - Anssi -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
