A New Perspective On TurboGears Identity

When I read Jeff Watkin’s post on identity management for turbogears all the pieces of identity finally clicked. I had some ideas that I sent to the TurboGears mailing list, but I didn’t fully understand identity so I could not see where my ideas fit in. Now I have a much better idea.

I spent a little time this morning creating a patch to better illustrate my thoughts. It is incomplete, but in my opinion a valuable step forward. But then again everyone thinks their ideas are great The patch is against revision 100.

Basically the patch tries to decouple the default behavior from the framework. I pulled it into a default module. Eventually I will post more details on the side effects of my changes, but I hope they will be brought up on the TurboGears mailing list.

When the patch is applied only the dev.cfg changed from what Jeff had in his post. In my dev.cfg my identity entries look like:

identity.on = True
identity.filters = [”turbogears.identity.filter.IdentityFilter”]
identity.failure_url = “/login”

Thanks to Jeff for all the work he has put into this. I am really exited about this particular subsystem. This is essential to almost every application that I create.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.

October 28, 2005 | Filed Under turbogears | Comments

My Blog’s New Look

If you have been here before then I don’t have to tell you how much has changed. I created a new flavour for Pyblosxom by combining a few different flavours I found other Pyblosxom blogs using. There is now a sidebar for easy navigation. As I get more and more into blogging I am sure that this page will constantly evolving.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.

October 16, 2005 | Filed Under blog | Comments

I Attended The First TurboGears Sprint

This past Saturday Mike Pirnat and I drove out to the first TurboGears sprint in Ann Arbor. The trip took a few hours, but our discussions kept it interesting. As we expected we arrived about a half hour late.

Basically Kevin Dangoor (the creator of TurboGears) had created a set of tickets to be worked on during the sprint. A ticket is roughly the equivalent of a small project or task. The group separated into pairs and each picked a ticket to work on. Mike and I got there after the others had separated into pairs so we got paired together.

We were tasked with adding Javascript animation capabilities into MochiKit. We looked at Scriptaculous and Dojo as examples of what to add and decided on integrating Scriptaculous into MochiKit. It was a bit of a challenge because neither one of us had any experience with any of those projects.

Unfortunately we were not able to switch partners or tasks. By the time everyone got setup and really got rolling the sprint was over. There wasn’t a ton of code produced, but the community was being built. I fully expect subsequent sprints to be very productive. It was definitely a worthwhile road trip.

Hopefully I will be able to get to the next sprint. The word out on the street is that it will probably stretch out over a couple of days. So I’d probably get a hotel room and bring the wife and kids. If a remote sprint ever happens I’ll be there for sure.

Other opinions on the sprint: