Daniel Fetchinson wrote: > I haven't looked at your code yet but have to say that I also don't > like very much the fact that I have to define what widgets are used in > the controller. It feels more natural to declare this in the template. > I don't claim to have a very precise opinion on what solution would be > the best but it just doesn't feel right how things are now (and > probably will be with TW) although I go with the flow and do it the TG > way anyway because it's not a really big deal. >
To those looking for another point of view on widget matters, I suggest looking at how Zope3 implements the MVC pattern. Views and Adapters (*) are, IMHO, a natural way to express presentation and editing of objects inside and outside the web interface -- in particular WRT reuse. I had a crush with Z3 before trying TG (*), and I miss the flexibility offered by that approach. In there, the template receives a 'view' object that is the form instance. Instance which is thrown away at the end of the request, btw. Very different from TG, and I don't think there is a single "correct" way. For sure, I would *love* to be able to render widgets with a @@view notation :-) (*) It took me a while to decide which way to go, although at the time, zope's form library was not as complete as TG's or TW. -- This e-mail (and any attachment(s)) is strictly confidential and for use only by intended recipient(s). Any use, distribution, reproduction or disclosure by any other person is strictly prohibited. The content of this e-mail does not constitute a commitment by the Company except where provided for in a written agreement between this e-mail addressee and the Company. If you are not an intended recipient(s), please notify the sender promptly and destroy this message and its attachments without reading or saving it in any manner. Any non authorized use of the content of this message constitutes a violation of the obligation to abstain from learning of the correspondence among other subjects, except for more serious offence, and exposes the person responsible to the relevant consequences. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
