On 2/13/06, Justin Johnson <[EMAIL PROTECTED]> wrote: > > > It's interesting. Django seems to be a more CMS oriented solution - > similar to Drupal/Civicspace - not surprising given it's news oriented > roots. That's not going to suit everyone though - me for starters. If > I had to use Django I'd be pulling out the admin stuff from the start as > it doesn't really fit in with our requirements. There's soon going to > be a huge explosion of web application diversity and not all models are > going to be based on CMS paradigm.
Yep. As I mentioned in a different thread a few days back: people are already writing CMSes on top of TurboGears. But, TurboGears itself is an application development framework first and foremost. > I personally think Kevin has made some good choices with TurboGears that > deliver a lot of flexibility and power. CherryPy's a great framework, > Kid's a very cool templating system that does The Right Thing with > regards to not encouraging code and logic integration into the > template. It's XML oriented approach is also going to become more > important as time goes on. SQLObject is a great ease of entry ORM. Thanks! > There seems to be quite a lot of grizzling about Kevin's choices too > which, quite frankly, aren't helping matters much. If Kevin and Co. had > been less clear minded about TurboGears it could have actually destroyed > the whole effort. If the choice of components seems disagreeable the > why not build your own? Fragmenting the TurboGears effort isn't going > to help. > > One of the main reasons that I think RoR has been so successful is > because it's a very cohesive and consistent bunch of components that > work really well together. That and endless fervent evangelism. :-) > > TurboGears seems to be heading the way of supporting lot's of different > components. Is this going to fragment the effort? Would it have been > better to stick with Kevin's choice of best of breed components and make > them better still? Let me be clear on this: where TurboGears has a solution to a problem, there will be one recommended (and properly documented) way to do it. There are good reasons for TurboGears to allow for template plugins, but that doesn't change the fact that TurboGears comes with Kid, the widgets are made with Kid templates, the documentation will use Kid, etc. If someone has a lot of non-HTML/XML templates they need to do, I wouldn't hesitate to recommend Cheetah for that task. The one solution to a problem focus is not going to change. That's a core part of the project. The solutions themselves will change in various ways over time, but for each release it should be clear to people how they should proceed to build their apps. Kevin
