I decided this year I am going to forego my Pycon dump, and focus on the news that matters most to my readership. There are plenty of reviews of talks, and I went to a bunch of good ones, had a great time at wsgi house, blah, blah, blah. What _you_ probably care about is what’s cutting edge in TurboGears, and the sprints are where it’s at.
We had 12 sprinters on day 1, I think 10 on day 2 and then 8, 4. So yeah, there’s some manpower behind the next-gen TG stuff. And that was our focus. I don’t think anyone lifted a 2.0 finger, all the effort has gone into 2.1. With Luke Macken’s help, we closed 21 tickets. I think we have all the road-blocks out of the way for the forthcoming b2 release, which will likely be the last beta before release candidates. The api is pretty solid now, I don’t expect to expand it an more, so it’s going to be feature frozen in b2. There are only 2 blocker tickets before 2.1rc1.
Mark Ramm and Jenny Steele overhauled the visual components of the 2.1 docs and came up with a better way of updating our public face. Jenny has also put forth an effort in c5t (a new cms based on mongo and tg2) to improve our image library capabilities. She also spent some time updating the TG admin so it looks way better now. I’ll post some screenshots when I do the 2.1b2 release.
C5t got quite a bit of love actually. Rick Copeland added Ming 0.2 support since the api changed a bit from 0.1. Christopher Brown fixed a bunch of the styling. Kevin Mitchell added some tests. Jason Galyon worked on per-page authz, and Jorge Vargas worked on the editor implementation. I created a new c5t.website project so that we can work on the core and the public image independently. This is valuable especially since c5t does not ship with TW1, but we wanted to add mongodb support to the admin on the website, and TW1 is required for Sprox to do it’s magic in the admin presently.
Kai Groner and Eric J (sorry I don’t know your last name) both made some contributions to Sprox. Eric added Ming support after I refactored the database orm later organization in Sprox. Ming is a layer on top of pymongo that allows you to enforce schemata in your collections. This is perfect for selecting validators (the validator in the schema becomes Sprox’s schema), and fairly simple to select widgets with. Eric had every provider test that works with SAORM working, except for one that looks like a pymongo bug on the limit operator. Kai worked on handling inline-forms in Sprox. Looks like most of the provider code is working, we just need to add in tw.dynforms in an intelligent way to hook the rest of the application up. While this is not a trivial task, it looks as if we are about half-way there for supporting inline forms. All of this work will go into sprox 0.7.
I also spent some time with Sprox, and added jquery support, but it’s not ready for release. At the end of the sprints I had a working jquery table with pagination in the TG Admin, but some polish is going to be required to get that fully working. When I’m done, you will be able to easily swap between nothing, dojo, and jquery, and mootools support, or mix and match at any level. You can also switch between mongo, or any rdbms SA supports, and hopefully couchdb soon. It’s kinda scary that’s true.
st desire to see put into action is that of a TurboGears CMS. There had been some work done last year by the guys at