The Pylons-less branch opens us the way of both moving to a different foundation or going on our own. I'm still not sure if we should move to pyramid or not, what I'm sure is that we should work more tightly with the Pylons project guys because in both the case we go on our own or use pyramid we will be based on many of the packages that are part of the pylons project. Any solution has to guarantee backward compatibility anyway.
What I know is: 1) From the Pylons package we were using about only 15% of the code as most of it was overwritten or monkey-patched in TG. 2) Jumping around changing the framework tools multiple times caused TG to get the fame of an unreliable framework 3) Many people I told them "woah, take a look at TurboGears, is cool" just answered me "it seems Pylons bloated, I think I'll go with plain pylons" and I want to avoid being the bloated dumb brother again :D So right now I'm still thinking about what is the best for the TG community, I'm slightly headed to the "go without pylons/pyramid dependency and cooperate on all the Pylons project packages we can share" way currently, but still not decided definitely. On Thu, Dec 15, 2011 at 8:48 PM, Christoph Zwerschke <c...@online.de> wrote: > Chris, good to see you cranking TG stuff again ;-) > > Maybe it's time to envision a more long-term roadmap, and keep that in mind > when working on TG2. E.g. how about our plans of joining with the Pylons > folks and basing on Pyramid? Are we heading into a different direction now? > The idea of TG is to be an opinionated full-stack framework like Django, but > with more freedom to exchange components. Which are our long-term > "opinions"? Will TG back out from doing client-side stuff? In TG1 we had TG > widgets and MochiKit. In my TG2 projects I use TW and tw.jquery heavily. I > think they were always an important part of the "full stack", but > unfortunately somewhat neglected. In my current projects I'm using even more > of JavaScript and even defected to Pyramid because I only need a very > lightweight and fast server component, TG2 would be overkill there. Anyway, > on the Pyramid mailing list I'm seeing many people who look for something > more full stack like TG2 or TG3 could offer. > > I'd also like to know whether Mark and the SF folks are still behind TG2 or > some kind of TG3. > > -- Christoph > > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To post to this group, send email to turbogears-trunk@googlegroups.com. > To unsubscribe from this group, send email to > turbogears-trunk+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/turbogears-trunk?hl=en. > -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to turbogears-trunk@googlegroups.com. To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
