> 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 -~----------~----~----~----~------~----~------~--~---
