Ok, now that I responded to everyone's posts I wanted to express my own thoughts on the subject.
First off, we are concentrating on what is WRONG with TW, not what is right, or what has been done BETTER than the competitors. If we seriously jam on what the features of TW are we will end up with some pretty damn good documentation. Ok. The reason people are blown away (or down) by TW is the complexity. This is why DBMechanic Primitives came to be. I am going to purposefully freeze the specs on the makeForm and makeTable functions. WHY? I want people to use toscawidgets to extend Primitive forms. I left a gaping wide hole for someone to add their own use-specific widgets, and if people start using the Primitives they will see the limitations and start using Toscawidgets to get the solutions they want. This is very much a Foot in Door approach. (As apposed to the Door in Face approach to DBSprockets.api, but that my friend is another story) Right now, besides docs, TW needs to look pretty. That's right, we need Ajax. Currently twAjaxTools is a crazy bit of code written by Claudio that works awesome in TG1. It will not work in TG2. It's also very hard to understand what is happening in the actual code, but what it basically does is modify the TG controller to add methods for use in the sending and receiving of JSon data. Sound Familiar? Right, Middleware. This code needs a re-write desperately for Toscawidgets, and probably DBSprockets to survive. Who will join me in this fight? cheers. -chirs. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
