> What appears on your wish list? Which ones above are important to you?
Pray forgive the length here - I've been brewing on some of these for a while. Other note: maybe best to reply using "Pycon: <subject>" rather than replying to this whole thread? In my opinion, the primary competition for TurboGears is not php - it's the web frameworks like phpnuke, drupal and Joomla!/Mambo. The nice thing about these is that you're running right out of the box (no programming) and it's very easy to write applications that fit into these frameworks. Where I'm mostly going toward is having the ability for there to be a few different "turbogears gui frameworks" out there (maybe oriented towards different audiences), but having applications run on any of these. So, Kevin already mentioned deployment using eggs. To go to the "next step" we need a few more things which are more ... introspective in nature. For instance: 1) Configuration. Right now, we have a python config file. The only issue with it is that there's no way to create a form from the config file that a user can edit at instantiation time. So, there would need to be a way to add a FormEncode/DataGrid item in there for configuration. There also needs a way for the application to store state on a per instance basis (I've got these 5 blogs, each configured differently). 2) Permissions. Yes, we have Identity. The problem is that everyone will have a different concept of what "admin" or "user" is. I really liked how Zope2 did their permissions: you put the name of the action as the permission. So "Edit Blog" would be the permission, not "Needs Admin". The thing Zope2 did badly was was giving the users one single obnoxious page to do the mapping for all applications at one time. That can be fixed at the framework level. Some frameworks could take the "user/group/role/permission" approach; others might take a more simple "user/permissions" - all depending on the target audience. 3) Services Some applications will end up becoming services that other applications could use. TG should be in the middle here, defining the interface, but allowing multiple applications to serve the need. For instance, picture a "News" application, which shows a summary on the main page, and allows a review/workflow for publication. You can easily see how a blog system might want to "publish" to the News service. Other ideas for services would be a search service (here's the url and the text: index it). Another might be a "user comment" service. Oh, I'll be at pycon as well for the whole time. Just haven't put my name up. Cheers, Gary Godfrey Austin, TX
