From: David Cantrell <[EMAIL PROTECTED]>
Sent: Tuesday, June 19, 2001 10:51 AM

> On Tue, Jun 19, 2001 at 10:20:37AM +0100, Steve Purkis wrote:
> > David Cantrell wrote:
> > > 
> > > Seriously, I agree 100% that you should strive to seperate application
> > > from your presentation as much as possible, but seeing that you can
not
> > > do this entirely, you may as well embed perl in your HTML and save
> > > yourself the trouble of inventing a whole new wheel.
> > 
> > That sounds like a contradictory statement there
> 
> I don't think so.  Whilst you should seperate application and presentation
> as much as possible, it's a recognition that you'll never be able to
> *entirely* seperate them, and so seeing that you're going to have to have
> *some* code mixed in with your presentation, you may as well re-use an
> existing language instead of inventing a new one.

But as Richard wrote yesterday, the point of mini-languages like the TT2
language is that they are specialised for one particular process[1]

In the case of TT2, you can write logic in it, but it's only very simple
presentaional logic (output one of these blocks for each thing in this list,
for example).

Another good reason, is that the people designing the output format aren't
necessarily the same people that write the data-gathering application. With
TT2 you can have a team of highly skilled and highly paid Perl programmers
doing extremely clever things to gather the data and a larger team of lowly
paid template designers producing the XML, HTML or whatever templates you
need to output the data. You can learn the TT2 language in an afternoon.
Perl, thankfully, takes a little longer.

Dave...

[1] You don't, for example, object to writing regexes in a mini-language
within Perl.

-- 



The information contained in this communication is
confidential, is intended only for the use of the recipient
named above, and may be legally privileged. If the reader 
of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  
If you have received this communication in error, please 
re-send this communication to the sender and delete the 
original message or any copy of it from your computer
system.

Reply via email to