Lee McFadden wrote: > Is that not what json.py is for? Maybe we should include a rule for > widgets in there by default so, when accessed via JSON, it just > returns the string "widget_instance" or something similar. > > I've never actually used json.py myself so I may have misinterpreted it's use.
You're missing the point. This is not about what json can and can't do, it's making the controller know about the output format for the data. What if we come up with a new CSV output format? What if it's RSS? What about XMLRPC? The point is that the controller shouldn't know or care. It just spits out data, the view determines what it looks like when it's returned from the server. Widgets are currently for encapsulating display and formatting logic for HTML output, so work in this paradigm if instantiated outside of the controller. Joseph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
