Re: Django Cheat Sheet

On Feb 13, 10:24 am, "John Sutherland" <[EMAIL PROTECTED]> wrote: > Issue 2 has been published: * The list_per_page Admin class option is now marked as an integer, not as an list. * CommaSeparatedIntegerField no longer has auto_now

Re: Django Cheat Sheet

I found one small mistake. CommaSeparatedIntegerField doesn't have auto_now and auto_now_add, so they should be removed from the appropriate place in the cheet sheet. Regards, Aidas Bendoraitis [aka Archatas] On 2/14/07, Julian Romero <[EMAIL PROTECTED]> wrote: > On 2/13/07, John Sutherland <[E

Re: Django Cheat Sheet

On 2/13/07, John Sutherland <[EMAIL PROTECTED]> wrote: > > > Hi all, > > Firstly, sorry for the cross-post. > > My employer, Mercurytide [1], as some of you may have seen in the > past, publishes white-papers on a monthly basis. This month it's > another Django themed one: a Django cheat sheet: > >

Re: Django Cheat Sheet

On 2/13/07, Matt <[EMAIL PROTECTED]> wrote: > > Cheers for all the feedback guys. Well, cheers to you in the first place... ;) Here's a reply to your questions so > far. > > As Malcolm Tredinnick pointed out in a private reply (and James Bennet > here), Django doesn't mind whether you pass it a t

Re: Django Cheat Sheet

Cheers for all the feedback guys. Here's a reply to your questions so far. As Malcolm Tredinnick pointed out in a private reply (and James Bennet here), Django doesn't mind whether you pass it a tuple or a lists; one can be substituted for the other. I think I'll remove this distinction in the

Re: Django Cheat Sheet

> Not really. Anything you can do to a tuple (which is, basically, > iterate over it, slice it and access specific items out of it) you can > also do to a list. A tuple is just a little bit more efficient when > you know you're dealing with something that isn't/shouldn't be > mutable. Actually, I

Re: Django Cheat Sheet

On 2/13/07, Rob Hudson <[EMAIL PROTECTED]> wrote: > I agree with another poster, adding FK and M2M and their options would > be a nice addition if there is room. Might be worth doing up multiple sheets, kind of like YUI does with their components. > Is there any reasoning to when an admin class

Re: Django Cheat Sheet

Very cool. I agree with another poster, adding FK and M2M and their options would be a nice addition if there is room. Minor nit... It says for version 0.95 yet there is a single template filter with footnote "In development version only." It seems like you might as well remove that. This also

Re: Django Cheat Sheet

> a Django cheat sheet: > > > > We've spent a fair bit of time on it and would really appreciate the > following: > > 1. That you download it; try it out and enjoy it! Good stuff. Had to squish it from A4 to 8.5x11 (rolls eyes at

Re: Django Cheat Sheet

Many many thanks, It helped me find the "js" admin feature ! I've not seen It before ! Useful! Picio 2007/2/13, Benedict Verheyen <[EMAIL PROTECTED]>: > > John Sutherland schreef: > > Hi all, > > > > Firstly, sorry for the cross-post. > > > > My employer, Mercurytide [1], as some of you may have

Re: Django Cheat Sheet

John Sutherland schreef: > Hi all, > > Firstly, sorry for the cross-post. > > My employer, Mercurytide [1], as some of you may have seen in the > past, publishes white-papers on a monthly basis. This month it's > another Django themed one: a Django cheat sheet: Super John, very useful ! Thanks

Re: Django Cheat Sheet

Hi John, On 13 Feb 2007, at 11:24, John Sutherland wrote: > > Hi all, > > Firstly, sorry for the cross-post. > > My employer, Mercurytide [1], as some of you may have seen in the > past, publishes white-papers on a monthly basis. This month it's > another Django themed one: a Django cheat sheet:

Re: Django Cheat Sheet

wow! On 2/13/07, Lars Stavholm <[EMAIL PROTECTED]> wrote: > > John Sutherland wrote: > > Hi all, > > > > Firstly, sorry for the cross-post. > > > > My employer, Mercurytide [1], as some of you may have seen in the > > past, publishes white-papers on a monthly basis. This month it's > > another Dj

Re: Django Cheat Sheet

John Sutherland wrote: > Hi all, > > Firstly, sorry for the cross-post. > > My employer, Mercurytide [1], as some of you may have seen in the > past, publishes white-papers on a monthly basis. This month it's > another Django themed one: a Django cheat sheet: > >

Re: Django Cheat Sheet

On 2/13/07 4:24 AM, John Sutherland wrote: > My employer, Mercurytide [1], as some of you may have seen in the > past, publishes white-papers on a monthly basis. This month it's > another Django themed one: a Django cheat sheet: This is awesome, John -- many thanks for putting it together :) Jac

Re: Django Cheat Sheet

On Feb 13, 11:24 am, "John Sutherland" <[EMAIL PROTECTED]> wrote: > My employer, Mercurytide [1], as some of you may have seen in the > past, publishes white-papers on a monthly basis. This month it's > another Django themed one: a Django cheat sheet: Good job John, thanks. Lorenzo --~--~

Re: Django Cheat Sheet - Lost?

On Sep 23, 2006, at 8:49 AM, Jon Atkinson wrote: > > Hi all, > > I've been looking for a copy of the Django cheat sheet (previous URL: > http://www.dobbes.com/media/pdfs/django_reference_sheet.pdf), but that > resource seems to have disappeared. Does anyone have a copy of this? You can find a c

Re: Django Cheat Sheet - Lost?

Search on google gave: http://www.woodpecker.org.cn:9081/classes/050925-CPUG/django_reference_sheet.pdf#search=%22django%20reference%20sheet%22 http://code.djangoproject.com/wiki/DjangoCheatSheet Chris --~--~-~--~~~---~--~~ You received this message because you

Re: Django Cheat Sheet - Lost?

Jon, I'm not sure, but I think that it was removed because it wasn't up to date. I have been working on my own cheat sheet, but it isn't ready for public consumption just yet. -- Nick Pavlica --~--~-~--~~~---~--~~ You received this message because you are su