Re: Refining Django admin look proposal

On Sat, Feb 6, 2010 at 6:02 AM, Russell Keith-Magee wrote: >  * Do we need to do this in phases - e.g., phase one for design > proposals, and then phase two for best execution of the design > proposal we pick? > >  * Who judges? I'm predisposed to say that the winner

Re: Refining Django admin look proposal

On Thu, Feb 4, 2010 at 1:44 AM, Russell Keith-Magee wrote: > On Thu, Feb 4, 2010 at 8:35 AM, tezro wrote: > > > > As the most obvious thing - here's the margin/padding problem on the > > left/right side of the page. One of a hundreds... > >

hide_email template tag

I know this is a bad time to bring up feature requests but I would most likely have forgotten to bring it up at a later date. Would a hide_email template tag be a good addition to the standard set of template tags in django? There's a snippet[1] on django snippets which serves as a good starting

Re: What do people think about the get_absolute_url proposal?

I brought this up during the 1.1 dev schedule and if I remember correctly the response was "let's have it painted red" and it seemed like it wasn't considered a practical problem. The reason I think this is an issue is the same reason that I get frustrated whenever I see a pull-style handle on a

Re: 1.2 Proposal: Add a few more tutorial steps

On Fri, Aug 21, 2009 at 4:10 PM, Dave Jeffery <djeff...@gmail.com> wrote: > > Does anybody have a copy (or know where I could a copy) of the completed > code for the Django tutorial? > Ok, I quickly ran through the tutorial steps, here is what the code was looking like at the

Re: 1.2 Proposal: Add a few more tutorial steps

On Fri, Aug 7, 2009 at 5:19 PM, Rob Hudson wrote: > > The tutorial ends here for the time being. Future installments of the > tutorial > will cover: > >* Advanced form processing >* Using the RSS framework >* Using the cache framework >* Using the comments

Re: 1.2 Proposal: django debug toolbar in contrib

On Mon, Aug 17, 2009 at 2:28 PM, Jacob Kaplan-Moss wrote: > > The reasoning was that we wanted the error pages to be somewhat > framework-agnostic; > we didn't want to impose our branding onto parts of *your* site. I'd > say a similar ethos should be expressed in the debug

Re: Proposal for contrib feature (DictionaryField in models)

On Tue, Aug 11, 2009 at 11:58 PM, Mark Ferrer wrote: > > You're right. I forgot about JSON. I guess it can be encoded and > stored as a JSON string and then decoded afterward. > See django-jsonfield: http://github.com/bradjasper/django-jsonfield/tree/master Personally I use

Re: 1.2 Proposal: Add a few more tutorial steps

On Fri, Aug 7, 2009 at 5:19 PM, Rob Hudson wrote: > > > If someone already had an idea on these wanted to add some more > details of what to cover under one of those topics, I (and others?) > can try to flesh one out during the 1.2 phase. > > Just a quick note that I would

Re: get_url() and get_url_path() for 1.1?

On Sat, Jan 10, 2009 at 1:11 AM, Malcolm Tredinnick < malc...@pointy-stick.com> wrote: > > There's no reason to mark it deprecated. It still works fine for what it > does. It just doesn't do what the name suggests, but, historically, that > hasn't been a real show-stopper for understanding

Re: get_url() and get_url_path() for 1.1?

hat causes practical problems. Cheers, Dave On Jan 9, 8:40 pm, Ludvig Ericson <ludvig.eric...@gmail.com> wrote: > On Jan 9, 2009, at 20:26, Dave Jeffery wrote: > > > > > Back in August of last year, there was a discussion about the > > confusing name of get_absolute

get_url() and get_url_path() for 1.1?

Back in August of last year, there was a discussion about the confusing name of get_absolute_url and it led to this doument by Simon Willison: http://code.djangoproject.com/wiki/ReplacingGetAbsoluteUrl After looking through the version 1.1 feature list (and rejected features)[1], this seems to