Just to toss out a data point, we started our last project with TG2/ Mako/GeoAlchemy (because we are doing location based stuff) and after the initial prototype, abandoned it for Rails 3 primarily because of sketchy documentation, and not particularly helpful responses to our questions on the list. I think there is real power in TG but some of the frameworks are just too hard to get your head around (ToscaWidgets - yes we wrote one - no we don't think it was worth it). That stupid zope transaction manager thing needs to go as well. It causes lots of problems and I don't think hardly anybody needs it. It should be an opt-in.
I like python, love GeoAlchemy (will have to add its geo capabilities to ActiveRecord in Ruby world) but it was just too hard to get off the ground with any kind of critical momentum using TG2. We did try. Just sharing our $.02 On Oct 29, 10:25 am, Christoph Zwerschke <[email protected]> wrote: > Am 29.10.2010 18:07 schrieb Diez B. Roggisch: > > > Also I'm very in general very satisfied with the technical aspects of > > TG2. I personally don't care about documentation (use the source, luke), > > and thus have always been able to unleash it's powers. > > Yes, but we need to care anyway since without proper docs you can't > attract new people and establish a larger community. Nor can you > convince coworkers or managers in your company to use TurboGears. In the > hand of Yedis TG is a great tool, but it has been just too hard for > Padawans to learn and master. > -- 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.
