Web templating/db tool with best designer/coder separation?

[Dave Cole]

>>>>> "Paul" == Paul Boddie <paul at boddie.net> writes:

>>  Whenever you build any toolkit you have to decide on the set of
>> problems that you wish to solve with the toolkit.  The smaller the
>> problem domain the more useful you can make the toolkit.

Paul> Indeed. Some kinds of applications may be addressed well by a
Paul> particular toolkit, and since you might spend most of your time
Paul> constructing those applications for customers, for example, it
Paul> would definitely be worthwhile abandoning "complete freedom of
Paul> expression" for something which gets the job done quickly,
Paul> effectively and cheaply. This is arguably where many
Paul> toolkits/frameworks fall down - by trying to be everything to
Paul> everyone, they become as complicated as the language they're
Paul> written in and don't always offer much more than the bare
Paul> language in doing a particular job. Consequently, people get the
Paul> temptation to write "rival frameworks" from scratch.

Touche.  :-)

- Dave

-- 
http://www.object-craft.com.au