Jeff, > Second, I think one of the things that makes TurboGears attractive to > new developers is that it is a complete solution out of the box. With > most other solutions, if you want some functionality, the answer is > "tweak this config file, paste this into your ABC file, and restart. If > that doesn't work, er, you're on your own."
Agreed. > Some have complained that Visit Tracking and Identity don't work > without a database defined. I realise it's not impossible to create a > meaningful Web application without a database, but I haven't seen many > in the last 11 years. And 1 or 2 additional SELECTs per request -- in a > Web application that actually does something more than print "Hello > World" -- is likely to get lost in the noise. I agree, I probably would not be recommending TurboGears for sites without a database. > Besides, we're at 0.9. If you look at the trend, the number of DB > queries has been dramatically reduced since when Identity first debuted > (I now load permissions and groups lazily instead of when the user is > first loaded) and I'm going to continue to work on this. Maybe it's > even reasonable to think I've got a solution to the extra SELECTs that > I'm not ready to roll into TG until after the rest of the code is working. Agreed. > I'd be delighted if quickstart included the option of customising what > features were included in the built project. But I'd encourage us to > have the default include all the rich pythonic-goodness that TurboGears > has. I agree. So please leave the goodness in for the moment. When someone has time to make these optional then fine. Regards Dave
