I concur with Ben's opinion concerning certain situations where SO,SA is a back step and does not improve programming efficiency. I rather have some way not to use any of those and just use "raw sql" . While short queries are ok, complexer ones get messy real fast , especially given the lack of full documentation and sufficient examples.
I also think that the current style and formating of documentation will lead to difficulties real fast. Why not start documentation from scratch for TG2.0 and have something like the apache manual as a style guideline ? It is paramount that documentation is up to speed with releases. Maybe any new version should only come out of beta when the docs are uptodate too. This would give a far better and mature impression. There are many good ideas in the cogbin , but only a few work out of the box. TG2.0 should also focus on getting some of the more promising ones to work like the quickstart facility. E.g. tgcrud. The documentation also needs to give a better understanding for the widget browser. The widget browser says source code and template and I believe many a new user is fooled that what is there can be copy pasted into the own kid file or controller. Only to find out it does not work that way. DB --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
