Several folks from Optio, and other Atlanta area companies are going to get together next week and sprint on a TurboGears related project, so I thought I'd let everybody here know about.
We're thinking that it would be a worthwhile experiment to try to reimplementing the core TurboGears API on top of Paste/Pylons and see what we get. It may be something useful, or it may not, but we figured it' is an interesting experiment at least. There are a couple of useful possibilities that we'd like to explore: Could you have object style dispatch by default, but which can be overridden with a routes style file for particular paths? Can we make testing even easier by implementing a Python template engine, which works like @expose(allow_json=True) to pass the python dictionary right through? This would be useful if you want to use your controllers from python, as well as for testing). Can we make transaction handling happen in middleware, and have the defaults be more easily overridden than they are now? So that some controllers will be automatically wrapped in a transaction, while others which only read from the DB, or don't touch the DB at all are not wrapped in a transaction. If you're interested in joining the sprint remotly, or just want to talk about the idea, you may want to joing the sprint's google group. http://groups.google.com/group/pygears/ -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
