First off, I'd like to apologize for taking so long to reply. I wanted to take some time to actually read the code, instead of just a quick glance.
So, here's the things I've noticed that should be dealt with differently in future: - Catwalk is deprecated. Check out tgext.admin, which you will find works out of the box on your quickstart. - In model/contacts.py, you define and bind a SQLAlchemy session. You probably don't want to do that normally. model/__init__.py already does this, so by simply importing your objects from model/contacts.py into mode/__init__.py, you will have SA working for free. - In controller/contacts.py, I personally prefer a style which looks like the Declarative style documented at http://turbogears.org/2.0/docs/main/Extensions/Crud/index.html#declarativehowever this is *purely* personal preference. Just figured I'd express my own. However, since that's *all* of the issues I could spot, I'd say it looks like a good job overall. On Sun, Feb 21, 2010 at 12:17 AM, Ryan Wilcox <ryanwil...@gmail.com> wrote: > Hi all, > > It was fun meeting some of you at the Turbogears BOF at PyCon on > Saturday. After the meeting I was inspired to go play with Turbogears. > > I got inspired to create an example app using scrape.py, a tool Guido > tweated about today (http://zesty.ca/scrape/). I thought it may make a > useful testing tool (and in fact it does!) > > So I set off to create a sample Turbogears app that use this to test > itself. I also used this project to learn what I could about > Turbogears 2.0 (also being my first TG2 project)... and ended up > documenting my experiences in a half-notebook half-guide README. > > I would be very interested in seeing people's feedback on this sample > project. It's not a normal beginner's project: I have database > migrations going on, pulled in Catwalk, got a RESTful controller up, > and got (as previously mentioned) testing. > > Additionally, I put this all in a git repository and put it up on > github, so people could see step by step what changes need to be made > for a certain bit of functionality. > > I'd be curious to what more experienced Turbogears hands think about > it - I'd welcome comments either here or in the github commits > themselves. > > So please check it out at: > http://github.com/rwilcox/turbogears2_setup_and_testing > > I hope this can be a help to the community and maybe we can learn a > little from it too (I for one would like to see more code generators > in paste... but that may be my Rails dayjob seeping through. > > Thank you all very much for this framework, > _Ryan Wilcox > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To post to this group, send email to turboge...@googlegroups.com. > To unsubscribe from this group, send email to > turbogears+unsubscr...@googlegroups.com<turbogears%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/turbogears?hl=en. > > -- Michael J. Pedersen My IM IDs: Jabber/peder...@icelus.tzo.com, ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/pedermj022...@hotmail.com -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to turboge...@googlegroups.com. To unsubscribe from this group, send email to turbogears+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
