Re: ANN: Updated Django Cheat Sheet
Issue 4 is out with a correction to the arguments for DecimalField in the Form Fields section. Thanks to Doug Van Horn for pointing out the error. Download it from http://www.mercurytide.co.uk/whitepapers/django-cheat-sheet/ Andrew --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: ANN: Updated Django Cheat Sheet
We've updated the cheat sheet to correct two typos: - The "default_if_none" filter is now correctly spelt (thanks to Aaron C. de Bruyn for pointing it out). - The "ForeignKey" model field is now correctly named (thanks to Nikos Delibaltadakis for pointing it out). Grab it from http://www.mercurytide.co.uk/whitepapers/django-cheat-sheet/ Andrew --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: ANN: Updated Django Cheat Sheet
On Sep 21, 8:23 am, "Nikos Delibaltadakis" <[EMAIL PROTECTED]> wrote: > Shouldn't ForeignKeyField to be just ForeignKey? > Am I missing something? No, you're absolutely correct -- thanks for spotting the error! We'll get a corrected version out ASAP. Cheers, Andrew. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: ANN: Updated Django Cheat Sheet
Shouldn't ForeignKeyField to be just ForeignKey? Am I missing something? 2008/9/10 Fraser Nevett <[EMAIL PROTECTED]> > > Just letting everyone know that we've released a new edition which > removes the PhoneNumberField and USStateField fields as discussed -- > thanks to all those who contacted us about this. > > The other common request we received was to have a version that worked > better with black and white printers. To this end, there's now a > grayscale PDF also available for download from our site: > > http://www.mercurytide.co.uk/whitepapers/django-cheat-sheet/ > > Regards, > > Fraser > > > On Sep 10, 11:30 am, Andrew Durdin <[EMAIL PROTECTED]> wrote: > > On Sep 9, 11:32 am, Vinay Sajip <[EMAIL PROTECTED]> wrote: > > > > > > > > > Nicecheatsheet. Hope it's not too late to offer a suggestion - it > > > would be useful to have the forloop special variables in thecheatsheet. > Not sure where you'll find room, though ;-) > > > > We had them there in an earlier draft, but there just wasn't room. > > They're not too hard to remember, though, hopefully? Off the top of > > my head: counter, counter0, revcounter, revcounter0, parentloop, > > first, last. > > > > You could write them all on a single post-it note and stick them to > > your monitor ;) > > > > Cheers, > > > > Andrew Durdin. > > > -- Nikos Delibaltadakis --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: ANN: Updated Django Cheat Sheet
Just letting everyone know that we've released a new edition which removes the PhoneNumberField and USStateField fields as discussed -- thanks to all those who contacted us about this. The other common request we received was to have a version that worked better with black and white printers. To this end, there's now a grayscale PDF also available for download from our site: http://www.mercurytide.co.uk/whitepapers/django-cheat-sheet/ Regards, Fraser On Sep 10, 11:30 am, Andrew Durdin <[EMAIL PROTECTED]> wrote: > On Sep 9, 11:32 am, Vinay Sajip <[EMAIL PROTECTED]> wrote: > > > > > Nicecheatsheet. Hope it's not too late to offer a suggestion - it > > would be useful to have the forloop special variables in thecheatsheet. Not > > sure where you'll find room, though ;-) > > We had them there in an earlier draft, but there just wasn't room. > They're not too hard to remember, though, hopefully? Off the top of > my head: counter, counter0, revcounter, revcounter0, parentloop, > first, last. > > You could write them all on a single post-it note and stick them to > your monitor ;) > > Cheers, > > Andrew Durdin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: ANN: Updated Django Cheat Sheet
On Sep 9, 11:32 am, Vinay Sajip <[EMAIL PROTECTED]> wrote: > > Nicecheatsheet. Hope it's not too late to offer a suggestion - it > would be useful to have the forloop special variables in thecheatsheet. Not > sure where you'll find room, though ;-) We had them there in an earlier draft, but there just wasn't room. They're not too hard to remember, though, hopefully? Off the top of my head: counter, counter0, revcounter, revcounter0, parentloop, first, last. You could write them all on a single post-it note and stick them to your monitor ;) Cheers, Andrew Durdin. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: ANN: Updated Django Cheat Sheet
Tnx, make a black/white version :) On Sep 4, 12:09 pm, Fraser Nevett <[EMAIL PROTECTED]> wrote: > With the release of Django 1.0, we're pleased to announce the release > of a completely updated version of our highly popular Django Cheat > Sheet which is crammed with a whole host of useful Django information: > > http://www.mercurytide.co.uk/whitepapers/django-cheat-sheet/ > > We welcome any ideas for improvements, corrections, or any other > feedback. > > On behalf of everyone here at Mercurytide, I'd like to offer our > sincere thanks to all those who have contributed to Django, and > especially to the core devs for all their effort. It's been a long > time coming, but everyone's hard work has made Django a truly awesome > framework. > > Fraser --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: ANN: Updated Django Cheat Sheet
On Sep 4, 6:46 pm, Fraser Nevett <[EMAIL PROTECTED]> wrote: > Thanks for all the feedback both on list and via email. > > Our plan is to wait a day or two to see if there are any further > corrections required and then to release an updated edition early next > week. At this time we'll also produce a alternative version which will > be more suited for non-colour printing. > Nice cheat sheet. Hope it's not too late to offer a suggestion - it would be useful to have the forloop special variables in the cheat sheet. Not sure where you'll find room, though ;-) Regards, Vinay Sajip --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: ANN: Updated Django Cheat Sheet
Le 4 sept. 08 à 12:20, Fraser Nevett a écrit : > > http://www.mercurytide.co.uk/whitepapers/django-cheat-sheet/ > > We welcome any ideas for improvements, corrections, or any other > feedback. Any chance to get a printable copy without colors, just a white background? My printer will thank you ;-). Best, David --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: ANN: Updated Django Cheat Sheet
> We welcome any ideas for improvements, corrections, or any other > feedback. Nice work, much appreciated. One thing did jump out at me though... In the Model fields section, USStateField and PhoneNumberField have been moved into localflavor: http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#MovedUSStateFieldandPhoneNumberFieldtolocalflavor --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
ANN: Updated Django Cheat Sheet
With the release of Django 1.0, we're pleased to announce the release of a completely updated version of our highly popular Django Cheat Sheet which is crammed with a whole host of useful Django information: http://www.mercurytide.co.uk/whitepapers/django-cheat-sheet/ We welcome any ideas for improvements, corrections, or any other feedback. On behalf of everyone here at Mercurytide, I'd like to offer our sincere thanks to all those who have contributed to Django, and especially to the core devs for all their effort. It's been a long time coming, but everyone's hard work has made Django a truly awesome framework. Fraser P.S. Apologies if this appears twice -- my first message didn't seem to get posted. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
ANN: Updated Django Cheat Sheet
With the release of Django 1.0, we're pleased to announce the release of a completely updated version of our highly popular Django Cheat Sheet which is crammed with a whole host of useful Django information: http://www.mercurytide.co.uk/whitepapers/django-cheat-sheet/ We welcome any ideas for improvements, corrections, or any other feedback. On behalf of everyone here at Mercurytide, I'd like to offer our sincere thanks to all those who have contributed to Django, and especially to the core devs for all their effort. It's been a long time coming, but everyone's hard work has made Django a truly awesome framework. Fraser --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Cheat Sheet
On Feb 13, 10:24 am, "John Sutherland" <[EMAIL PROTECTED]> wrote: > <http://www.mercurytide.com/whitepapers/django-cheat-sheet/> 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 and auto_now_add parameters. * The distinction between lists and tuples has been removed. M. -- Matt Riggott. Dictated but not read. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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 <[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: > > > > > <http://www.mercurytide.com/whitepapers/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! > > 2. Give us feedback, we know it's not going to be perfect first time, > > so let us know: [EMAIL PROTECTED] > > 3. You publicise it: it would be awesome to get it on the digg front > > page [2]; but put it on your blog, your del.icio.us or where ever... > > > > > > > Great work, thanks. > A couple suggestions here: > * if you give away the original format (it seems it's InDesign) others can > improve, adapt, make new versions and you will get more publicity (add a > by-attribution license) > * move the legend to your web site, symbols are quite obvious and you will > save lot of space for additional stuff like usual command line options or > whatever > -- > Julián > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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: > > <http://www.mercurytide.com/whitepapers/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! > 2. Give us feedback, we know it's not going to be perfect first time, > so let us know: [EMAIL PROTECTED] > 3. You publicise it: it would be awesome to get it on the digg front > page [2]; but put it on your blog, your del.icio.us or where ever... > > > Great work, thanks. A couple suggestions here: * if you give away the original format (it seems it's InDesign) others can improve, adapt, make new versions and you will get more publicity (add a by-attribution license) * move the legend to your web site, symbols are quite obvious and you will save lot of space for additional stuff like usual command line options or whatever -- Julián --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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 tuple or a lists; one > can be substituted for the other. I think I'll remove this > distinction in the next issue. > > For reasons of space I left out details on foreign keys, many-to-many > relationships and, because they're undergoing change, one-to-one > relationships. They seem to be popular enough that I'll look at > adding a second page to include them. there still is some confusion (judging by the questions in django-users) about related models lookup, so the combination of related fields (FK, M2M and 1to1) and db_api should be very useful... > > I was a little naughty and included some functionality only available > in the development version. I followed the docs in this respect, but > I guess for consistency I should remove this. > > I want to try and keep it up-to-date: when 0.96 is released I'll find > time to issue a new version with changes from the newforms-admin > branch et al. great news > Rob Hudson's right: list_per_page should be an integer, not a list. I > knew I'd miss something! I'll change that in the morning. > > Does anyone have any requests for what to include on a second page? > (The biggest internal request has been for an example of the fields > options in the Admin inner class - something we're forever looking > up.) perhaps a list of db_api functions and field lookups? also a list of form fields and widgets would be useful, if you want to stick with stable features, what about generic views - including their context and parameters. > A loud 'Thank you!' should go to the designer, Ed, for managing to > make all that text look presentable. Cheers, Ed. Thanks Ed ;) > > M. > > -- > Matt Riggott. > Dictated but not read. > > > > > -- Honza Kr�l E-Mail: [EMAIL PROTECTED] ICQ#: 107471613 Phone: +420 606 678585 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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 next issue. For reasons of space I left out details on foreign keys, many-to-many relationships and, because they're undergoing change, one-to-one relationships. They seem to be popular enough that I'll look at adding a second page to include them. I was a little naughty and included some functionality only available in the development version. I followed the docs in this respect, but I guess for consistency I should remove this. I want to try and keep it up-to-date: when 0.96 is released I'll find time to issue a new version with changes from the newforms-admin branch et al. Rob Hudson's right: list_per_page should be an integer, not a list. I knew I'd miss something! I'll change that in the morning. Does anyone have any requests for what to include on a second page? (The biggest internal request has been for an example of the fields options in the Admin inner class - something we're forever looking up.) A loud 'Thank you!' should go to the designer, Ed, for managing to make all that text look presentable. Cheers, Ed. M. -- Matt Riggott. Dictated but not read. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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 think "list_per_page" should be an integer, not a list as it is on the cheat sheet. If so, that means only the js option is a list. Which means everything that has a multiple option list is a tuple already, with the exception of the js list. For some reason I thought ordering took a list. -Rob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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 option is a list and > when it is a tuple? I tend to default to tuple since I don't want to > have to go look it up every time. Can admin options be standardized > to tuples across the board to make it easy? 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. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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 reminds me of a question I've been meaning to ask... Is there any reasoning to when an admin class option is a list and when it is a tuple? I tend to default to tuple since I don't want to have to go look it up every time. Can admin options be standardized to tuples across the board to make it easy? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Django Cheat Sheet
> a Django cheat sheet: > > <http://www.mercurytide.com/whitepapers/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 the silly American paper metric when A4 is so much more asthetic) but it came out legibly. > 2. Give us feedback, we know it's not going to be perfect first time, > so let us know: [EMAIL PROTECTED] I noticed that ForeignKey, OneToOne, and ManyToMany field types were missing...I don't know if there's too much detail required for those to smash them into what little space you have left, but they're certainly hairier corners that it would be helpful to have on a cheat-sheet. I remember hearing rumors that OneToOne may be deprecated, but I can't find any evidence to back that up. Perhaps if you need the space, a 2nd page could contain FK and M2M (and perhaps O2O) as well as the date/time formatting codes that the sheet currently only references. The whole thing could then be printed 2-sided and laminated to prevent food & beverage damage ;) Just my ponderings. Still helpful even without the above changes/additions. -tkc --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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 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, > Benedict > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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, Benedict --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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: > > <http://www.mercurytide.com/whitepapers/django-cheat-sheet/> Awesome! Thanks for sharing this! If only I had that this morning while on the train! :) Cheers! Geert -- Geert Vanderkelen http://some-abstract-type.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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 Django themed one: a Django cheat sheet: > > > > <http://www.mercurytide.com/whitepapers/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! > > 2. Give us feedback, we know it's not going to be perfect first time, > > so let us know: [EMAIL PROTECTED] > > 3. You publicise it: it would be awesome to get it on the digg front > > page [2]; but put it on your blog, your del.icio.us or where ever... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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: > > <http://www.mercurytide.com/whitepapers/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! > 2. Give us feedback, we know it's not going to be perfect first time, > so let us know: [EMAIL PROTECTED] > 3. You publicise it: it would be awesome to get it on the digg front > page [2]; but put it on your blog, your del.icio.us or where ever... Brilliant! /L --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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 :) Jacob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Django Cheat Sheet
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: <http://www.mercurytide.com/whitepapers/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! 2. Give us feedback, we know it's not going to be perfect first time, so let us know: [EMAIL PROTECTED] 3. You publicise it: it would be awesome to get it on the digg front page [2]; but put it on your blog, your del.icio.us or where ever... Cheers, John. [1] <http://www.mercurytide.com/> [2] <http://digg.com/programming/Django_cheat_sheet> -- [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
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 copy here, but it's not up to date - pre 0.91 from July 2005. http://www.punteney.com/files/django/django_reference_sheet.pdf Don --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
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 are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Django Cheat Sheet - Lost?
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? --Jon --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
