For relatively simple apps, Witango makes it easy to put separate rules from presentation. Rules go in actions, and presentation goes in resultsHTML.
But as things get complex, there can be an incentive to use metatags in place of actions to reduce the size of files. One extreme would be to write SQL statements with lots of <@IF>, etc, so that the logic is embedded in the SQL query, and one DirectDBMS action could generate a range of queries. I kind of shy away from this, even though it would be convenient, and would tend to use IF actions to split my queries into distinct cases.
On the other hand, I have tended to put some business logic into my ResultsHTML, so I only have to maintain presentation element. Here's an example -- a new record form. If it's a regular user, the owner field is fixed by the userid; if it's an admin user, I present a select form element to allow the owner to be chosen. Here, I would take the position that I would rather embed some logic in presentation, than have to maintain HTML variants for each class of user.
I suppose that an Object-Oriented approach could work, but that seems like a lot of effort, and I'm not sure that encapsulating logic and presentation in a class file is any better from a long-term maintenance perspective.
What do others do in practice?
bill
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
