On 6/27/07, Mark Ramm <[EMAIL PROTECTED]> wrote: > > Recently there have been a number of requests for more clarity about > the future of TurboGears, and since I've been involved heavily with a > couple of experimental projects designed to help us explore our > options, I'd like to help clarify things as best I can. > Thanks for the update Mark
> The goal was not just to re-implement things, but to see if that > re-implementation actually improved the readability, flexibility, and > ease-of-mantinance of the TurboGears project. In other words, we > wanted to make TurboGears: easier for new developers to work on, > easier for us to maintain, and more flexible so we can take advantages > new python web developments in the future. > KISS all the way! > And that brings us back to TurboGears 2.0. In addition to the current > TurboGears API, the new tg package will support all kinds of new > features that will make our user's life easier. Many of these > features are the direct result of our integration with Pylons, because > we'll be getting access to a lot of great stuff they've already done. > And we'll be sharing almost all of our infrastructure code with > another group of great developers. > I'm sorry to be asking the hard questions but what will people win for using TG2 instead of "plain" pylons? why will someone that didn't had the joy of coding in TG1 will want to learn TG2? which are the core TG2 features, that is what is TG-only and what we get from pylons? I have half an answer there, dict-dispatch and @expose and of course all the great stuff in http://trac.turbogears.org/browser/projects and http://turbogears.org/cogbin I think we should write something on why TG+pylons is better then pylons, I say we as in TGpeople but not me because I honestly don't know anything about pylons. > At the same time, we'll be working to support people who want to > develop and maintian sub-projects for automatic CRUD (like Catwalk or > the Django interface) outside the TurboGears 2 core. Our hope is that > these tools will be broadly usable by anybody who is working withing > the context of a framework that implements the Web Server Gateware > Interface standard. Ultimately I think Pylons, TurboGears, Paste, > Zope, and all kinds of other python web developers toolkits will be > working together on creating great tools for rapid development. that will be a great day. May I suggest we start defining entry points for all the TG stuff? maybe have turbogears.tools for things like paginate,scheduler,feed controller,etc. and of course reinstate the extensions entry point for identity et all. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
