Randal L. Schwartz wrote: > The problem is that the application...model...view...controller.
One of the problems with MVC (or the excessive evangelism of it), is that it can fool you into thinking that your problem breaks down nicely into three separate concerns when it almost certainly doesn't. The symptoms you describe sound like they are caused by a failure to identify and separate a particular concern. The fact that you're repeating data/functionality in more than one place is a dead give-away. So perhaps you need to figure out what out letters you're missing from the MVC soup. It is often as simple as that: just figure out what noun(s) describes the behaviour that you're trying to isolate. Do you need to define a Role, for example, to mediate between User and Task? Or perhaps the part you're missing is a Visitor to abstract an interaction between a location and an operation. Or a Schema/Schedule, or a Machine/State/Action, or something else (take your pick from the Design Patterns book). Having said all that, I've built dozens of form based web applications, some large, some small, and I have't yet come up with a general solution that I'm happy with. It is not an easy problem to solve. Good luck! A _______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.template-toolkit.org/mailman/listinfo/templates
