> I'm sorry but I think your expecting way too much of the API. The idea > behind widgets is to get the most common uses of data presentation patterns > in an easy way. > > Why you need widgets for what your doing? all you need is a texfield (normal > plain xhtml) and a normal plain controller method (with json on) that will > access the database. and do whatever you like with it.
The textfield has an onkeypress handler that sends a JSON request. The sending of the JSON request probably should be in a widget and the method that responds probably should be in a controller. If I understand TurboGears philosophy correctly.. > Widgets api is not like Swing or AWT or wxWindows, it's' not made to cover > ALL graphical code. > > rethink your issue without Widgets and let me know if that fix your > thinking. Yes it does, kind of. You are right that I'm expecting to much of Widgets. For complicated views, it seems like it is much smarter to go widgetless than to try and compose it using TurboGears Widgets. -- mvh Björn --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
