percious schrieb: > The reason we no longer pass the form into the template dictionary is > because it is not data. Therefore we add the form to the template > context which defines how the template should be drawn, not what data > should be displayed. There was a discussion on this a while back if > you search around.
Ok, I see. It seems the main point is that if you want to use a controller for both html and json, then passing widgets in the return dict will be unnecessary and potentially causing problems with jsonification. So it is a better practice to pass these via the template context instead. Seems reasonable to me, this should just be better explained and documented. -- Christoph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
