I can see where you're going with this. :-) Keeping the widgets separate is probably better simply to avoid mixing two kinds of things (HTML vs. code).
Our consultants probably won't be web developers. They'll be people with a strong math or scientific background, not traditional programmers but the kind of folks who know their way around SQL, Excel, and and maybe math languages like SAS or R. Barry ----- Original Message ---- From: Jorge Godoy <[EMAIL PROTECTED]> To: [email protected] Sent: Saturday, February 2, 2008 5:58:24 AM Subject: [TurboGears] Re: Formetto: widgets in the template, not in the controller Em Friday 01 February 2008 11:16:12 Barry Hart escreveu: > I'm intrigued by this discussion and where it'll end up. > > I'm working on a app development team that hopes to become more of a > component toolbox team. Consultants would take our components and > build/customize an application. The consultants will not have strong > development skills, so if we can reduce the number and complexity of files > they touch, it'll make theirs and our lives simpler. And what you think would be better for them? Putting logic inside templates -- and in the hands of web designers with dream weaver... -- or putting their logic in the controller? -- Jorge Godoy <[EMAIL PROTECTED]> ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
