On Thu, Aug 21, 2008 at 10:31 PM, cd34 <[EMAIL PROTECTED]> wrote: > > I am not sure if the original poster asked the question he intended. > I think he wanted to ask -- if you were developing a site today, would > you use TurboGears 1 or TurboGears 2? > I'll say it depends on your needs if you like CP a lot tg1.5 seems like a good candidate, that said tg2 is stable enough to be used in production (at least for me) and you will probably want it, now be aware that some updates can break your code (but mostly one import here or there) as it isn't still out.
> Facing the same issue, I saw no real reason to not use TurboGears 2 > with the assumption that our application would be developed over the > course of a few months and TG2 would be mature enough during our > testing and development and release would be timed close enough with a > stable TG2. TG2 has some significant advantages over TG1. As far as > code maturity, TG1 has a slight edge, but, TG2 is really a thin layer > coordinating many established and developed products that have a > relatively large installed base. > > To answer the original question, as someone not involved with the > development, I think that trunk TG2 is probably stable enough to be > considered over TG1. > > It was because of the ORM that I chose TG2 over django. django's > documentation eclipses TG2 and they now support sqlalchemy. Did I misread this or you said django can be used with SA? As far as I know the only efforts this way are an almost-death[1] branch (2yrs old) and a very experimental project [2] anyway just wanted to clarify that, even with [2] django is build in such a way that most if not all of the existing apps won't work out of the box, which is kind of the big killer for django. [1] http://code.djangoproject.com/browser/django/branches/sqlalchemy [2] http://code.google.com/p/django-sqlalchemy/wiki/Roadmap > TG2, I felt like an outsider when trying the example code. Quite a > bit didn't work and I wasn't sure if I was just dumb and didn't know > what I was doing, or there were assumptions made that any beginning > programmer should have known. As it turns out, there were a number of > typos. Documentation will either turn TG2 into an web development > firm's open source toolkit, or a web framework to be widely adopted. > I'd prefer the latter. > > While I do feel that the time based releases are able to be planned > around, a roadmap with estimated completions is just fine with me. > Even a basic guideline like 2Q2009, 2H2009 would be fine for me. > While I've not completely tested all of the framework functionality > that I need, I feel relatively comfortable that TG2 will handle my > requirements. > Agrred on that. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
