On 1/21/07, Paul Johnston <[EMAIL PROTECTED]> wrote: > > It's auto admin system is great, particularly > because it is configurable. IMO this is the only place where django beats TG, although I really don't like the idea of having the model objects define the strings for the GUI.
> The problem I found with Django was that if > you wanted to do something that doesn't quite fit its approach, you're > back to doing things the long-hand way. *cough* Ruby on Rails *cough* > It doesn't have the whole > widgets/validators system that TG has, although they are working on this > with "newforms". I think TW will be better for this. > The Django controller is more flexible, being based on > regular expressions, but I find CherryPy's syntax is preferable for my > work. So, all things considered, I decided to use TG and my decision is > reinforced the more I learn. you can get something similar in TG with a little magic http://routes.groovie.org/ and http://docs.cherrypy.org/writing-your-own-dispatcher > Many people (including Guido) have commented that it would be great to > combine the efforts of the projects, to produce one "hyper framework". > I'd say in the short term, merging TG and Pylons is a more likely > prospect, but perhaps Django could be brought closer. yes I'll like that too many people doing the same thing is a waste of time. > I believe > ToscaWidgets already contains pretty much all the functionality of the > Django "widgets" in newforms. If Django started using TW, we would have > the beginnings of a meeting of minds. Fastdata2 could then be modelled > after (or even replaced by) Django's auto-admin system. maybe when django finish their port to SA if they keep some abstraction the auto-admin stuff could be ported. > All the project > already seem to be moving towards SQLAlchemy as the ORM. The controller > is a harder one to merge - the regex/expose mechanisms will just suit > different people. I for ones don't like it, regex are good for somethings IMO this is not one of them. > But perhaps the controller will become as pluggable as this is one of the things all the WSGI goodness is supposed to solve. > the template engine currently is. If all this happened, Django would > effectively just be TG, using a particular choice of controller and > templating engine. > > Frameworks are becoming more like distributions every day... well I love that :) my biggest problem with ALL frameworks is that sometimes it's harder to get around it then just doing what you need, TG is very good at not getting on your way. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
