> Once the more advanced features of TurboGears are more set in stone > (widgets, validation, identity, etc.) I plan to write the next part of > the to-do list tutorial to incorporate those. After that I think all > that's left is to show how to deploy it anywhere and how to refactor > the existing code.
Fromhere, it looks like widgets are pretty stable -- there are some minor tweaks around the edges, but I've been working with them quite a bit lately, and they to have the right amount of polish and stability for this point in the TurboGears release cycle. The only thing they *really* need before 1.0 is better docs! And I don't think identity is going to change significantly before 1.0 either, so the core is pretty stable. I'm still delving into validation and error handling, but I think the API for that is pretty stable too. So, FastData is the only thing that needs a lot of love -- which I assume is why Kevin pulled that out into a separate experimental package. -- 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" 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 -~----------~----~----~----~------~----~------~--~---
